Your seat is saved

We saved your seat.

Here is what the next seven days actually look like — the workshop, the manual pass, the weekly check-ins, then the audit — before any code touches your workflow.

Reply within two working days, frompunchlist-studio@polsia.appBack to the pilot formGet the newsletter

The next seven days

What the manual pass actually looks like.

Seven days of hands-on work — first a workshop at the shop, then a manual run by us alongside your team, then the audit. No automation touches your workflow before week three, and not then unless the manual pass justifies it.

What this isn’t

Not a SaaS dashboard. Not a generic AI agent. Not a Zaps folder someone on your team built in an afternoon. The useful distrust comes from a frank audit of the hours, in writing, before any build starts.

  1. DAY 01 · Day 1–2

    We read your form by hand and reply by email.

    Signed reply from punchlist-studio@polsia.app within two working days — in the founder's voice, quoting back the workflow you wrote about so you know we actually read it. The founder is the one doing the workshop; nothing is handed off to a queue.

  2. DAY 02 · Day 2

    We schedule the kickoff before the dust settles.

    A 30-minute call, your number or a Zoom, our calendar link or yours. The window is locked before the workshop so the date is on both our sides by day three.

  3. DAY 03 · Day 3–4

    Half a day with whoever runs the workflow at the shop.

    We sit in on the workflow — usually one interview per operator who actually carries the work, often a half-day at the shop. No deck, no demo. We come in alongside.

  4. DAY 04 · Day 5–10

    We run the workflow by hand, by us, in your tools.

    For one or two weeks we do the work ourselves — same tools, real customers, every minute logged. No shadow CRM, no demo accounts, no Zaps folder. Until week three, the only thing touching your workflow is a human, with a notepad and a stopwatch.

  5. DAY 05 · Day 7

    A 15-minute call, mid-pass.

    Mid-week check-in: status on tabulated hours, the friction we have found, what we'll change before week two. You're never more than a calendar invite away from a status update.

  6. DAY 06 · Day 8–10

    Same day, same length, every week, until the manual pass wraps.

    A recurring weekly check-in cadence, booked on the shared calendar for the duration of the engagement. We show up at the same time on the same weekday so it's never a hunt for an open hour — yours or ours.

  7. DAY 07 · Day 11–14

    You get the audit, in writing, before any build.

    Manual-run hand-off: a tabulated before-and-after, hour-by-hour log, what the build has to beat, plus our recommendation (build or don’t). The manual pass is the proof — if the numbers do not justify a build, we leave you with the receipts and the engagement is done, no half-built zaps folder to maintain.

Bring to the kickoff

What to have ready for the workshop.

You do not need a deck or a CRM export. You need the parts of the workflow that already live on paper, in someone’s head, or in a shared inbox — the parts we will be running by hand for the next two or three weeks.

  • BRING · 01

    Your last two invoices, and your last change order.

    Printed or on a screen — both fine. We use them to time the re-quote back to the quote that came in, and to see what the change order loses between the workshop and the office. Five minutes of paper beats an hour of walking us through the workflow onstage.

  • BRING · 02

    A one-line weekly map of where the time leaks.

    On day one we ask you to draw, in writing, the workflow you want us to fix — which day, which hours, who carries it. A napkin is enough. The map does not need to be pretty; it needs to be the version your foreman would defend, not the version you would defend at a trade show.

  • BRING · 03

    A contact at the shop who actually runs the workflow.

    Not the owner’s assistant — whoever carries the work. The workshop is a half-day at the shop with that person, riding along. If we can’t reach them by name when we reply to your form, the engagement won’t start.

  • NEVER BRING

    What we will never ask you to send in writing.

    Passwords, tool logins, customer PII — none of it, not in the form, not in the workshop, not in the audit. We sign an NDA before day one if your pricing, customer list, or job notes are sensitive, and we don’t train anything on your data without a written note from you.

Next step

Book your kickoff interview, or just reply to the email.

Pick a 30-minute window this or next week. We'll come back with a confirmation from punchlist-studio@polsia.app. Or, if you’d rather pick a window inline, just punch a time on the call below — we’ll come back with a confirmation.