Every engagement opens the same way: a written scope lands in your inbox within 72 hours, and no invoice moves until you’ve signed off on it. This page walks the first week of that process — what the owner delivers, and how your input shapes it.
Every engagement starts the same way, on the same five-day cadence. Here’s what week one looks like — and what you’ll have in your inbox by Friday.
Brief arrives
You send the rough idea — links, a one-paragraph note, screenshots, or a full brief. Any input lands the same path; nothing is too short to read.
Scoping agent reads it
An AI scoping agent reads the input, drafts a requirements document in plain English, and runs a budget reality check against the tier you picked.
Draft scope within 72 hours
A written scope lands in your inbox within 72 hours. You accept it as-is, edit the answers to redraft, or send the full intake to move forward.
Sign-off, then kick-off
You sign off on the scope. Work starts the next business day, with the first pull request reviewer notes attached before the first commit is reviewed.
Every engagement ships four steady deliverables from week one. They are how a scoped brief becomes a deployed release, and how an honest scope is signed off without a status meeting.
Written requirements doc
Five short sections covering problem, target user, recommended approach, a budget reality check, and the open questions still on the table.
Acceptance criteria
Concrete, testable conditions attached to every milestone — the same doc a reviewer reads before signing off on a PR.
Per-PR reviewer notes
A concise summary on every pull request — what changed, what to test, what to watch — so a single click is the only merge step.
Friday release digest
A written digest in your inbox every Friday afternoon — code shipped, code merged, code queued, plus any open incident triage.
Ready to send the full brief? The intake form at /intake is the right entrance — or use the 5-question scope first if you’d rather see a draft before sending the long form.
The brief shape can be as rough as a paragraph with a few links or a stack of screenshots — whatever is in front of you. The scoping agent is trained to read fragments and turn them into the four-part scope we walked through above, and it works the same on a one-line brief and a five-page spec.
If you’d rather see a draft before sending the full intake, the 5-question scope on the right is the lighter path. Five short answers, a draft requirements document in seconds, and the option to send the long form once the draft is in the right shape.
Either path lands in the same inbox and the same 72-hour SLA. The only thing that changes is whether you’re starting with the rough idea and asking us to do the writing, or starting with the long form and submitting it directly.
Not ready to send a full brief? Answer five short questions and we draft a plain-language requirements document in seconds. Read it, edit your answers if you want a different draft, or send the full intake when you’re ready.
Engagements start with a 30-minute scoping call. We send back a written scope within 72 hours — and we don’t send invoices until you’ve signed off on it.
Not ready to brief yet? Scope it first →
Or email wingman-stack@polsia.app with a one-paragraph brief.