Skip to content
Grow without adding admin hires

Don't hire the next data-entry clerk. We'll build the system instead.

You are hiring someone to retype documents into your systems. Before you do, give us 14 days with that one workflow. You get a process map, a working proof on your real documents and a fixed quote to automate it.

The call is with the founder, who also does the work. No deck, no sales team. Twenty minutes is enough to tell whether your workflow fits.

Fee
$4,900 fixed
Billed
On delivery, day 14
Credit
100% to the build
Scope
One workflow
Or start in writing

Tell us the role. We tell you if it fits.

The founder replies within one business day. No sequence, no sales team.

01 / What lands on day 14 Six deliverables, one pack, one call

Everything you need to decide, in plain language.

The pilot is the deep dive and the assessment of one workflow, the one in your job post. It is not the build. It gives you the numbers and the fixed price to decide on the build with your eyes open.

  1. Process map

    The workflow as it runs today: what comes in, which systems it touches, who hands off to whom, how many items a week and how long each one takes.

    One page, one diagram
  2. Exception list

    Every variant and edge case we find in your sample, each tagged automate, human review or out of scope. This is the part most vendors skip and most projects die on.

    A tagged register
  3. Working proof on your documents

    A sample of 20 to 50 of your real documents, run end to end. Extraction or entry, with an accuracy table: items, fields, correct, needs review. No claims without the table.

    Live run plus accuracy table
  4. Build scope

    A fixed-scope statement of work for the full system: milestones, acceptance tests and the human-review path for every exception on the list.

    SOW draft, ready to sign
  5. Fixed quote

    One number for the build, plus the option of a fractional automation engineer on retainer after go-live. The pilot fee comes off the build in full if you sign within 60 days.

    Fixed price, 60-day credit
  6. 30-minute readout

    We walk you through all of it on a call and leave you with a yes or no decision in front of you. Nothing in the pack needs decoding.

    Decision call
02 / The 14 days About two hours of your team's time in total

Day by day, so you know what is happening and when.

Nothing is invoiced until the last line. The dates are calendar days from kickoff.

  1. 1-2days Kickoff

    A 45-minute call. You name the workflow owner and share a sample of real documents plus read-only or sandbox access to the target system. NDA first if you want one.

    Kickoff notes, sample received
  2. 3-5days Shadow the work

    A recorded walkthrough with the person who does it today. We time each item and list every system it touches.

    Draft process map, time baseline
  3. 6-8days Build the proof

    Extraction, validation rules and output into a sheet or your system sandbox, running on the sample.

    Proof v1 on your documents
  4. 9-10days Exception hunt

    Every sample item goes through. Every variant is logged. We agree the human-review path with the workflow owner.

    Exception list, accuracy table
  5. 11-12days Scope and quote

    We write the build scope and price it, then check it against our engagement rules: fixed scope, change orders, no open-ended time.

    SOW draft, fixed quote
  6. 13day Review

    Internal review and polish. The pack is produced as a PDF from our proposal system.

    Assessment pack
  7. 14day Readout

    The 30-minute call, the pack in your inbox and the invoice for the pilot. Only now.

    Decision in hand, invoice sent

Scope is one workflow. If the job post covers several, the call is where we pick the one with the most retyping in it, and the Systems Audit covers the rest.

Book 20 minutes
03 / How we keep it honest The terms, in writing, before the call

No logos, no testimonials. The method and the money terms instead.

We are a small firm and we would rather show you how the pilot protects you than borrow someone else's credibility.

  • Nothing upfront

    The pilot is invoiced on day 14, when the assessment pack is in your hands. Not at kickoff, not at signature.

  • Credited in full

    Sign the build within 60 days and the $4,900 comes off the build price as a line on the SOW. The pilot is a down payment, not a fee on top.

  • No claims without the table

    The proof runs on your documents, not a demo set. The accuracy table shows items, fields, correct and needs-review counts, per field.

  • Exceptions on the record

    Every variant found in the sample is written down and tagged. The ones we will not automate are listed as out of scope, in writing, before you spend on the build.

  • Your documents stay yours

    The sample is used for the proof only and deleted on request after the readout. We sign your NDA before we see a single file if you ask for one.

  • The founder does the work

    The person on your kickoff call maps the workflow, writes the proof and prices the build. No handoff to a junior team after the sale.

04 / What happens after A decision, not a dependency

The pilot ends with a yes or a no. Both are fine.

If you say yes

Yes: the build

The process map and exception list become the scope. The accuracy table becomes the acceptance tests. The proof code becomes milestone one, hardened, not rewritten. The pilot fee comes off the price.

If you say no

No: you keep the pack

You keep the process map, the exception list and the accuracy table. If you still hire, the new person starts with a written procedure and a list of the cases that trip people up.

Optional

After go-live

Optional retainer: a fractional automation engineer who monitors the system, handles the exceptions that change and extends it as the business does. One active build at a time.

05 / Questions

What people ask before they book.

Anything else: [email protected]

What do you need from us?

About two hours of the workflow owner over the 14 days: a 45-minute kickoff, a recorded walkthrough and a short exception review. Plus a sample of 20 to 50 real documents and read-only or sandbox access to the system the data goes into. Access to production is never required.

How do you handle our data?

The sample is used for the proof only. It is stored in an access-controlled workspace, not shared with anyone outside the engagement, and deleted on request after the readout. We sign your NDA before receiving files if you want one. Regulated data, including HIPAA and financial records, is handled under written terms agreed at kickoff.

What if it does not work on our documents?

Then the accuracy table says so, and that is the finding. You still get the process map, the exception list and a written explanation of what would have to change. We will not quote a build that the proof does not support, and you are not obliged to sign anything.

Is the pilot the build?

No. The pilot is the deep dive and assessment of one workflow. The build is a separate, fixed-scope statement of work that the pilot produces, with the pilot fee credited in full if you sign within 60 days.

What happens after the pilot?

You decide on the build with a fixed quote in front of you. If you go ahead, the proof becomes milestone one and the build follows the SOW. After go-live, you can keep a fractional automation engineer on retainer to monitor and extend the system, or run it yourself.

Who does the work?

The founder. One person takes the kickoff, builds the proof and writes the scope, so nothing is lost between a salesperson and a delivery team.

Which workflows fit?

Anything where a person reads documents and retypes the data into a system: supplier invoices, customer orders, insurance certificates, intake forms, claims, applications. If the job post says data entry, order entry, AP clerk or processing specialist, it is probably a fit. The 20-minute call settles it.

When do we pay?

On day 14, when the assessment pack is delivered. The invoice is for $4,900, due on standard terms. There is no deposit.

Two ways to start

Twenty minutes now, or a note and a reply tomorrow.

Either way, the next step is the same: we look at the workflow in the job post and tell you whether a pilot would pay for itself.

Book 20 minutes with the founder

Pick a slot on the calendar. The call is a conversation about the workflow in your job post, nothing more.

Or start in writing

Tell us the role. We tell you if it fits.

The founder replies within one business day. No sequence, no sales team.