Audit

Audit your week.
Six questions. One named workflow. Hand-graded follow-up.

Every trade shop has the workflow that eats evenings — the one nobody owns, nobody can name, and everybody routes around. Six short questions below: the server scores them server-side and names one of seven kinds on the other side.

How to read the estimate

Server-scored, plain-English, no demo required.

The line under the form is not a funnel. Every answer you type travels to /api/audit, is scored there, and comes back as a workflow-kind label + a numbered hours-saved pill. There is no hidden assumption about who you are or what your shop does.

What this isn't. Not a scoring engine for sales. Not a guided tour. The score is the same code the studio runs against your answers when you email us — the result panel is the preview.

  1. STEP 01

    Six short questions

    Your trade, crew size, hours on paperwork, the recurring admin task, current tools, and the biggest pain. Two minutes. No SaaS pitch on the other side.

  2. STEP 02

    Server-scored estimate

    On submit the server runs the math — base hours × your crew multiplier, then a keyword pass that names one of seven canned workflow kinds.

  3. STEP 03

    One paragraph, then the lead form

    The recommendation shows on the same page. Below it, leave a name + email so the studio can read every one and reach back within two working days.

What happens after you submit

Three steps. Hand-graded. Two working days.

The audit is the front of a known funnel — submit, hand-graded follow-up, fixed-fee pilot if it's the one we'd pick. No auto-drip, no "demo next Tuesday", no Slack-channel handoff.

  1. STEP 01

    Submit → 24h review recap

    The row lands in the studio inbox. A hand-grader (with a cron for the auto-reply) reads it within roughly twenty-four hours and writes back the same flow everyone gets.

  2. STEP 02

    Hand-graded follow-up email

    Within two working days, a named person at the studio replies with the workflow we picked, the hours we agreed on, and the next decision you have to make.

  3. STEP 03

    Fixed-fee pilot offer

    If it's the one we would pick, we send a scoped pilot offer — fixed fee, named workflow, run by hand before any code ships.

See it in the wild. A real engagement, tabulated to the quarter hour before any code was written.

Read the case study

The form

The six questions.

Type the answers — the server scores them. Look at the named workflow on the right. Drop your name and email at the bottom if you want the follow-up; otherwise nothing leaves the page.

  • The math runs server-side in /api/audit. Same rubric, every time.
  • The lead form posts to the installed /api/waitlist. The same inbox the rest of the site reads by hand at punchlist-studio@polsia.app.
  • Skip the lead form and nothing is sent. The result panel stays in this tab until you close it.
SIX QUESTIONS · TWO MINUTES

Just you counts as one. Best guess is fine.

Whole hours, 0–60. Best guess is fine.

A sentence is enough — name the workflow.

Comma-separated. Even “paper logbook” counts.

A sentence is enough — the words help us name the kind.

Scored server-side — does not leave the browser until you click.

Bring us the workflow

The single workflow your shop is losing the most hours to. We will do it by hand first.

Save a seat on the first 10 with a thirty-second form. We reply within two working days.

Save my seat on the first 10or email punchlist-studio@polsia.appEstimate scored server-side · follow-up read by hand.