You have the list. This is how it gets shorter.
Every operations leader has a list of things that should be software and are still email, PDF and a spreadsheet. This page is for the person who owns that list: what gets built first, what you actually do during the four weeks, and why the second item takes less time than the first.
What gets built
Customer portals, renewals, claims and service intake, partner onboarding, commission statements, the internal tool that replaces the spreadsheet.
What you do
Write a brief in your own words. Read a task list. Click through a preview as each role. Approve.
What you do not do
Read code, wait for a developer, write a specification document, run a project office.
How long
A first preview within days. Integration in the test environment in week three. Production in week four.
Which item first
The first slice should be the one that hurts most and depends on the fewest systems.
Renewals that run on PDF forms
Individual links, reminders on a schedule, data landing in the system of record instead of being re-keyed. This is what TAS built.
A customer portal with service requests and status
Clients raise requests and track them; account managers answer them. The classic first slice, and what Broker Collective started with.
Partner or broker onboarding
Documents in, checks done, approval recorded, access granted. Replaces a shared inbox and a tracking sheet.
Claims or application intake
A structured form with validation instead of an email attachment, routed to the right queue with a status the customer can see.
How your week changes
Monday: the brief
One page in your vocabulary: outcome, roles, data, rules, what done means. The product manager agent turns it into tasks and asks what it still needs to know.
Tuesday: the task list
You read it in ten minutes and edit it in chat. Every edit here costs a sentence; every edit after the build costs a task.
Thursday: the preview
You sign in as a client and as an account manager on a preview URL. You try the thing a client should not be able to do. You ask for a filter in chat; it is there an hour later.
The following week: your team
The people who will run the workflow test it in the test environment, connected to the real system. Their feedback becomes tasks. Then you approve the release.
Why the second item is faster
The roles already exist
Client, account manager, admin: defined once, reused by every application after the first.
The integration already exists
The connection to the system of record is a task that was already built and tested. The next workflow uses it.
The branding already exists
Logo, colours, email templates and, if you serve several brands, deployment labels are set once.
Your team already knows the loop
Brief, task list, preview, approve. The second time, nobody needs the walk-through.
The rules already exist
What had to be true the first time, brand rules, required fields, the approval that must be recorded, sits in the application's Knowledge and applies to every task after it. Nobody re-explains it.
What operations leaders ask
Do I need IT for this?
For the first slice, no. For the integration in week three, one hour from whoever knows the system of record. There is a page for them.
What if I do not know how to describe it?
Bring the current process: the PDF form, the spreadsheet, the email template. The scoping session turns them into a brief with you. The blog has a one-hour method and a gold standard brief you can copy.
Can I change my mind after the preview?
That is what the preview is for. Changes are new tasks. Small ones land within the hour.
What does my team have to learn?
How to write a short brief and how to read a task list. Both take one afternoon. Nobody learns a tool.
Bring the item that hurts most.
Thirty minutes with the founder: the brief, the first task list and a preview on screen. You leave with a written pilot scope.
Plan your first app scope in one hour