How do I design a new business process from scratch?
Updated
Start with the outcome the process must produce and work backward. List the steps, the owner of each step, the handoffs, and what done looks like. Run it once by hand, fix what breaks, then document and automate the stable parts. CorZen turns that into weekly tasks with an owner on each, on the timeline you choose.
Working backward from the outcome
- which needs
- Access to client tools grantedAccount manager
- which needs
- Intake form returnedClient
- which needs
- Welcome email and intake form sentSales
- which needs
- Contract signedTrigger
Example: client onboarding at a small agency.
What does a process design plan look like?
This is a sample 90-day roadmap for the Create New Process category with the Architect approach. CorZen also builds 30-day, 60-day, custom, and ASAP timelines. Your own plan changes with your market, your tools, and how many hours your team has each week.
Design
Weeks 1–4
- Week 1Define the outcome and how you'll measure it.
- Week 2Map the steps, owners, and handoffs.
- Week 3List the tools and inputs each step needs.
- Week 4Review the design with the people who will run it.
Pilot
Weeks 5–8
- Weeks 5–6Run it by hand on real cases.
- Week 7Log every failure and where it happened.
- Week 8Revise the design.
Formalize
Weeks 9–13
- Week 9Write the standard operating procedure.
- Week 10Automate the stable steps.
- Week 11Train the team.
- Weeks 12–13Measure cycle time and error rate.
How do you define the outcome of a new process?
Write one sentence that says what starts the process, what it produces, and how fast. Then pick two numbers to measure it by: how long it takes, and how often it goes wrong.
When trigger, result within time.
ExampleWhen a client signs, they have a kickoff call within 5 business days, with the brief, tool access, and first invoice in place.
How do you map the steps, owners, and handoffs?
Draw one lane for each person or team, and place every step in the lane of the person who owns it. Each time the work moves to a new lane, that’s a handoff.
This example has five steps and four handoffs. Handoffs are where new processes usually break, so each one needs a clear “done when” rule before the next person starts.
What does each step need to run?
For every step, write down who owns it, what “done” means, and the tools or information it needs. Then review the table with the people who will run the process.
| Step | Owner | Done when | Needs |
|---|---|---|---|
| 1. Welcome email | Sales | Email and form link sent the day the contract is signed | Email template, intake form link |
| 2. Intake form | Client | Every required field filled in | Form with required fields, a named contact |
| 3. Tool access | Account manager | Logins work for every tool on the brief | Admin contact at the client, access checklist |
| 4. First invoice | Finance | Invoice sent to the billing contact | Billing contact and PO number from the form |
| 5. Kickoff call | Account manager | Call held, notes and next steps shared | Completed brief, agenda template |
How do you pilot a new process?
Run the process by hand on real cases before you document or automate anything. Log every failure with the step where it happened.
Failures by step, six pilot clients
- 1. Welcome email0
- 2. Intake form3
- 3. Tool access2
- 4. First invoice1
- 5. Kickoff call0
From the failure log
| Step | What broke | Fix |
|---|---|---|
| 2. Intake form | Not returned after 3 days | Reminder on day 2 |
| 3. Tool access | Client contact wasn’t an admin | Ask for the admin contact in the form |
| 4. First invoice | Sent to the wrong person | Add a billing contact field |
Example pilot. Fix the step with the most failures first. Here, two of the three fixes are new fields on the intake form.
Which steps should you automate?
Automate a step only if it ran the same way in every pilot case. Keep a step manual if it changes from case to case or needs someone’s judgment.
- 1. Welcome emailSame every timeAutomateSend when the contract is signed
- 2. Intake form reminderSame every timeAutomateSend on day 2 if the form isn’t back
- 3. Tool accessDifferent for every clientKeep manualEach client uses different tools
- 4. First invoiceSame every timeAutomateCreate from the form’s billing fields
- 5. Kickoff callNeeds judgmentKeep manualThe account manager runs it
How do you know the new process works?
Measure the same two numbers you set at the start, on every case that runs through the finished process.
9 days→4 days
3 of 6→0 of 8
Example numbers: the six pilot clients, then the next eight clients after the fixes.
How does the plan change on a 30- or 60-day timeline?
The order stays the same on every timeline: design, pilot, then formalize. Shorter timelines run fewer pilot cases. Custom and ASAP timelines keep the same order.
| Timeline | Design | Pilot | Formalize |
|---|---|---|---|
| 90 days | Outcome, map, inputs, team review, weeks 1–4 | Real cases by hand, failure log, revision, weeks 5–8 | SOP, automation, training, measurement, weeks 9–13 |
| 60 days | Outcome, map, team review, weeks 1–2 | Real cases by hand, revision, weeks 3–5 | SOP, training, measurement, weeks 6–9 |
| 30 days | Outcome and map, week 1 | A few real cases by hand, weeks 2–3 | SOP and first measurement, week 4 |
A 30-day plan has time for only a few pilot cases, so leave automation until the process has run unchanged for a while.
Should you design a new process, standardize how work is done, or keep it lightweight?
All three are ways to create a new process. Pick the one that matches what’s missing today.
Design from scratch
The work is new, or nobody has a way of doing it yet.
Standardize
The work gets done, but differently by each person.
Lightweight
A small team needs just enough process to move fast.
How does CorZen build this plan for you?
Tell CorZen your goal. Pick Create New Process, then the Architect approach, then a timeline: 30, 60, or 90 days, a custom length, or ASAP. A short AI interview asks about your niche, what makes your business different, the tools you already use, and how much time your team has each week.
CorZen then builds a roadmap for that timeline, broken into weekly tasks. Every task has an owner, and a task can have more than one. On Team and Business plans, AI agents can draft deliverables for individual tasks, such as a first draft of the standard operating procedure.
Which template should you look at next?
Frequently asked questions
What is the difference between a process and an SOP?
The process is the work itself: the steps, owners, and handoffs. The standard operating procedure (SOP) is the written version that tells someone how to run it. Write the SOP after the pilot, once the steps have stopped changing.
How many cases should you pilot a new process on?
Usually five to ten real cases. That's enough for the weak steps to fail at least once, and few enough to fix the design quickly.
Should you automate a new process right away?
No. Run it by hand first. Automating a step before it's stable means rebuilding the automation every time the step changes.
What should a standard operating procedure include?
The outcome and what starts the process, each step with its owner and "done when" rule, the tools it needs, the exceptions, and who to ask when something doesn't fit.
Can AI agents help design a process?
They can draft the work for a person to review, such as a process map, a standard operating procedure, or email templates for each step. On CorZen's Team and Business plans, AI agents can draft deliverables for individual tasks in your plan.