Skip to content
Softlane
Placeholder

Placeholder copy. This page follows the homepage outline. It is not locked marketing language.

The AI workforce platform for agencies

Digital workers for agencies. No AI team required.

Hire digital workers trained for a role, train them on your process and each client, and run them under your account managers. Every action is approved by your people and logged. Web QA is available now. More roles are on the way.

Book a demoStart with a pilot
  • Built for agencies, by an agency owner
  • Isolated per client
  • Chrome and Safari engines, every eight hours
  • Priced per worker

Fig 1 · Illustrative — Isolated from every other client.

One client account · one hybrid team
Work flows right to left: the worker runs, the specialist verifies, the account manager decides.

Your account manager

Approves · reports · sets the budget

Your specialists

Trains · verifies · teaches rules

Digital workers

Runs every 8 h · proposes · never acts alone

Your client receives reports in your template, under your brand.

The build temptation

Everyone is tempted to build it.

A prototype on one site feels close. The second client is where the bill starts. Placeholder timeline, not a case study.

  1. Month 1

    A prototype checks one staging site.

  2. Month 2

    Engines, viewports, and a queue get added.

  3. Month 3

    The next client wants a different checklist.

  4. Month 4

    Approvals, tickets, and a report template show up.

  5. Month 5

    Isolation, secrets, and an audit log become the work.

  6. Month 6

    It holds for one client. The second client starts the bill again.

The invisible bill

People
Specialists stop doing client work and start keeping the tool alive.
Spend
Browsers, models, and storage run with no cap and no owner.
Maintenance
The checklist changes. The tool does not ship the change.
What stays yours
  • The client relationship
  • The checklist and the brand on the report
  • The decision to publish
What we build and run
  • Engines, schedules, and evidence
  • Isolation between client accounts
  • The audit log and the hard cap

You didn't start an agency to run AI infrastructure.

Side by side

Build it, or hire the worker.

A qualitative close for the person who owns the agency. No figures until they are set. Placeholder rows.

People

If you build it

Specialists become the people who maintain the tool.

With Softlane

Specialists train a role and review what it finds.

Hidden cost

If you build it

Engines, queues, models, and the second client.

With Softlane

One worker, one monthly amount, a hard cap.

Time

If you build it

Months before the first report a client can read.

With Softlane

A pilot measured in eight weeks.

Keeping up

If you build it

Every browser and viewport change is yours.

With Softlane

Web QA runs on Chrome and Safari engines.

Reliability

If you build it

The demo works. The eighth run flakes.

With Softlane

A failure is reproduced once. A person confirms it.

Credibility

If you build it

A side project sitting next to client work.

With Softlane

Reports leave under your brand, after approval.

Placeholder comparison. Qualitative until the founder adds numbers.

How it works

Hire it, train it, let it run.

Your people decide what goes out.

  1. 01

    Hire
    Pick Web QA for one client account.

  2. 02

    Train
    Your specialist loads the checklist, the brand, and the rules.

  3. 03

    Run
    The worker checks Chrome and Safari engines every eight hours.

  4. 04

    Review and approve
    A specialist verifies. An account manager decides what leaves.

  5. 05

    Report
    The client gets your template, under your brand.

Every correction a specialist makes can become a rule for the next run.

Forward the complaint. Get back evidence.
  1. 01The account manager forwards the client's complaint.
  2. 02The worker runs the relevant checks.
  3. 03You get evidence: what changed, where, and the severity in words.
  4. 04A person decides whether it becomes a ticket or a line in the report.

Integrations

  • JiraNow
  • EmailNow
  • SlackNext
  • ClickUpNext
  • AsanaNext
  • LinearNext

The roster

A worker is a role, not a chat box.

Web QA is the role you can hire now. The others are named so you can see the shape of the roster. Placeholder status labels.

Web QA
Available now
Checks the site on a schedule, grades what it finds, and waits for a person.
SEO & site performance
In development
A later role for the checks your team already repeats on rankings and speed.
Analytics reporting
In development
A later role for the monthly numbers an account manager already assembles.
A role your agency repeats
Tell us
If your team does the same job every week, it can be a worker.
Web QA
Available now
Job posting. Placeholder duties.

What it does

  • Runs your checklist on Chrome and Safari engines.
  • Runs every eight hours, or when an account manager asks.
  • Captures evidence and proposes a severity, written out in words.
  • Does not send a client report or open a ticket on its own.

Trained on

  • Your agency's house checklist.
  • This client's rules and the findings a person has suppressed.
  • The last report a person approved.

Illustrative findings

Severity is written out. Colour does not carry the meaning alone.

  • Contact form throws a console error on Chrome, 1366×768.Critical
  • Checkout total is covered by the button on Safari, 390×844.High
  • Hero image shifts after load on Chrome, 1920×1080.Medium
  • A decorative rule is missing alt text. Informational.Low
  • Footer copyright year matches the current year.Pass

Fig 2 · Illustrative — Green is a worker step. Amber is a step a person takes. The word is always next to the colour.

From finding to fix

  1. 01

    Worker
    Run
    The worker opens the page on each engine and viewport.

  2. 02

    Worker
    Grade
    It names the finding and attaches the evidence.

  3. 03

    People
    Verify
    The specialist confirms, rejects, or teaches a rule.

  4. 04

    People
    Approve
    The account manager decides what the client will see.

  5. 05

    People
    Ticket
    A ticket opens only after that approval.

  6. 06

    People
    Report
    The report goes out in your template.

Nothing reaches a client without passing through amber.

For your team

Three buyers. Three different mornings.

The owner, the account manager, and the specialist do not want the same thing. Placeholder scenes, marked illustrative.

Pain

Growth means more people, or more tools the team has to run.

What you get

A worker on a client account, priced per worker, with a hard cap.

Result

You add capacity without hiring an AI team.

Fig 3 · Illustrative — Two ways to grow

  1. Hire another person for every new client.
  2. Add a worker to the team you already have.

Isolation

Ownership by client, expertise by domain.

Harbor & Co. belongs to Priya, but its Web QA work is trained by Tom. Names are illustrative.

Fig 4 · Illustrative — Three layers. Client data never moves up into the blueprint.

  1. 01

    Client layer

    This account only
    Sites, rules, evidence, and reports. Never mixed with another client.

  2. 02

    Agency layer

    Shared inside the agency
    The house checklist, the report template, and the people. Not shared outside.

  3. 03

    Softlane role blueprint

    How the role works
    Shared across agencies. It never carries a client's pages or secrets.

Security and governance

What you can tell the client's IT contact.

Plain controls. No compliance badges, because we are not claiming a certification.

Isolated per client
Each client account is a hard boundary. Another client's pages, rules, and evidence are not in the run.
A person before any action
The worker proposes. A person approves a ticket or a client report.
Audit log for everything
Who approved, who changed a rule, and which run produced the evidence.
Budgets with hard caps
Work stops at the cap you set. Going past it takes a logged decision.
Safe by default
Staging first. Production is an explicit choice. Checkout stops before payment.
Business use only
Built for client delivery, not for wandering the open web on your behalf.

Pilot

Start with one client account. Measure it in eight weeks.

Placeholder plan. Weeks and measures are a draft, not a contract.

  1. Weeks 1–2

    Connect one site, load the checklist, and agree the cap.

  2. Weeks 3–6

    The worker runs. Your people verify and approve.

  3. Weeks 7–8

    Read the eight weeks together. Then decide on a second account.
What we measure together
  1. 01Findings a person confirmed
  2. 02Findings a person rejected
  3. 03Hours the account manager did not spend re-checking
  4. 04Tickets opened only after approval
  5. 05Whether the client report went out under your brand
Pricing
Per worker, per month.

The amount is the worker, the runs, and the cap you set.

Never a surprise invoice.

No figure is published until it is set.

Placeholder. No price is shown on purpose.

Start with a pilot

Straight answers

Questions we expect before a pilot.

Placeholder answers. Replace with the locked FAQ before launch. Ten questions, drafted from the outline, not copied from a final script.

Founder

Why an agency owner built this.

GS
This sentence needs Gurmail's own words.

Gurmail

Founder, Softlane

Placeholder. Needs Gurmail's own words and a photo. Do not publish the stand-in line.

Demo

See it on your own client's site.

Thirty minutes. Bring a site and the checklist you already use. We walk the worker on that site. You see where a person still decides.

Thirty minutes, on your site.
No booking form in this starter. The button opens an email. The label comes from the shared site config.

hello@softlane.ai

Book a demoStart with a pilot