Scoper.pro

HOW IT WORKS

Two paths. Pick the one that fits.

Both paths start with the same form. We read it and recommend. If you are not sure which path suits you, submit the form and we will tell you.

PATH 1 — SELF-SERVE

If you want to build it yourself

  1. STEP 1 — 3 MIN

    Submit the form

    One form, shared across both paths. Tell us the workflow — what triggers it, what steps it involves, what the output is, and what tooling you currently use. We read every submission.

  2. STEP 2 — WITHIN 24 HOURS

    We pick the closest kit

    We read the form and pick the closest kit from our library. The kit is scaffolding — prompts, folder structure, stack picks, a first task — generic enough to adapt to your specifics. If we cannot see a sensible match, we will say so before charging you.

  3. STEP 3 — SAME DAY AS MATCH

    Kit lands in your inbox

    A GitHub repo or zip arrives by email. Inside: a system prompt tuned to your archetype, a first-task prompt, follow-up prompts, worked examples, evaluation criteria, a troubleshooting guide, and a roadmap of the next 3–5 milestones.

  4. STEP 4 — 1–2 HOURS SETUP, THEN YOUR PACE

    You build with Claude

    Install Claude Code (or use Claude.ai web or Cursor), paste the kit, and run the first task. The kit is structured so you get visible output on day one. From there you work through the roadmap at your own pace.

PATH 2 — DONE FOR YOU

If you want it built for you

  1. STEP 1 — 3 MIN

    Submit the form

    Same form as the kit path. Tell us the workflow, the team, the volume, and the current tooling. No discovery call required to submit.

  2. STEP 2 — 30 MIN

    Scoping call

    We get on a call to agree the workflow, the scope, and what “done” looks like. We confirm the fixed fee and the four-week timeline before any work starts.

  3. STEP 3 — 4 WEEKS

    Audit and build

    Week one: a half-day workshop with your team to map the current workflow in detail. We build from there. You review at week two and week four. At the end: the tool, the prompts, the evaluation harness, a runbook, and a handover session.

  4. STEP 4 — OPTIONAL, ONGOING

    Retainer

    If the tool needs ongoing care — model updates, prompt drift, new edge cases — a retainer is available at A$2,500 + GST per month. Most clients run the tool themselves after handover. The retainer exists for the minority where ongoing care is worth the cost.

WHAT WE NEED FROM YOU

What each path requires

Kit

  • 30–60 minutes to fill the form carefully — the quality of the match depends on the quality of the brief.
  • Access to a Claude environment (Claude.ai web, Claude Code, or Cursor).
  • One or two sample inputs from the real workflow so the kit can be tuned to your actual data.
  • Someone on the team willing to run the first task and iterate.

Consulting

  • Half a day from the right people in week one — the person who owns the workflow, not a delegate.
  • Sample data or representative cases we can use to test the tool before handover.
  • Two review checkpoints at week two and week four.
  • A decision-maker available for a short call if scope questions arise mid-build.

NEXT STEP

Both paths start with the same form.

Submit the form and we will read it within one business day. If a kit fits we will confirm and send it. If consulting is the better match we will say so. If neither path is right for your situation, we will tell you that too.

Start with the form