Money
Starter vs The week vs several workflows
Tobiloba Odejinmi · 6 May 2026 · 6 min · 999 words
Direct answer
One workflow is $5,000: a single process, built, tested, handed over. The week is $7,500: the same job plus the next-process plan, proper APIs, monitoring, and thirty days of support. Several workflows start at $15,000 when you already know you need more than one live path and someone owning the join. Start at the smallest scope that matches the work, not the slide.
- $5,000 is one process with a handover, not a company program.
- The week is $7,500 because monitoring and the next plan are part of the job.
- $15,000+ is for more than one live workflow and a deeper join.
- You can start small. You cannot fake a second process into the first invoice.
What is One workflow for $5,000?
One workflow is the tight build. We sit down. We pick the process that costs the most hours and is boring enough to automate. I connect it to what you already use. It goes live. You get a write-up and a call. That is the job.
It is enough when the process is already clear and the tools are reachable. It is not enough when you need me to stay on the monitoring, or when you want a knowledge store and a sequenced plan for the next quarter. Those sit in The week on purpose.
What is The week for $7,500?
The week is four steps and a live process. Day one we pick the work. Days two and three we map the steps, the tools, and the cases a person still has to see. Days four to six I build. Day seven it is live, with docs and someone who can explain it.
You also get a plan for what to automate next, proper API connections, monitoring, and thirty days of support. I put those in this tier because a seven-day build without a watch or a next step is how projects die in week three. Most people book this one.
What is Several workflows at $15,000+?
This is not two copies of $5,000 with a smile. The second process changes the first. Shared logging. Shared escalation. A join between tools that was optional on day one and is now load-bearing. I price from $15,000 because the architecture has to be owned, not improvised.
Buy this when you already know the processes and you can name the owner who will live with both. If you are still arguing about which pile matters, you are not in this tier. You are in a thirty-minute call.
Who should start at $5,000?
A team with one painful, written process and a person who will own the exceptions. Internal copying between two tools. A first-pass CV screen. A follow-up note that already has a template. Support answers your team already gives.
If the process is still a vibe, $5,000 will feel expensive because we will spend it on mapping you were not ready to finish. I would rather you wait a week and write the steps than buy a starter you cannot hand to anyone.
When is $7,500 the better buy?
When you want the thing watched after it goes live. When the APIs are real, not a zap that will rot. When you want a straight answer about the next process so you do not wander. The extra $2,500 is not a nicer PDF. It is the difference between a handoff and a week that still has a spine.
If you are in health, lending, or any path that moves money, I will push you here. I have seen what happens when monitoring is 'we will add that later'. Later is how Monday morning fails.
When do you actually need $15,000+?
When support and follow-up share a customer record. When hiring screens have to write back into the same ATS the recruiter lives in, and a second workflow has to stay consistent. When ops wants two live paths and one person who can explain both at 2am.
IBM’s 9% Frontier Firm number is not a reason to jump here. Scale is a reason. A week-one build that works is still capability ROI. Several workflows can get you toward realized ROI on more than one desk. It still is not a strategy transformation by itself.
Can you start small and add later?
Yes. That is how I prefer it when the company is honest about staffing. Ship one process. Pay tokens, pay the reviewer, watch the logs. If realized ROI shows up, we talk about the next path. If it does not, you learned cheaply.
What I will not do is let a $5,000 line absorb a $15,000 scope because procurement has one box. Scope lives in the process, not in the purchase order nickname.
Questions people ask
What do I get for $5,000?
We pick the process. I build one live workflow in the tools you already use. You get a write-up and a handover call. You do not get a thirty-day support window or a roadmap for the next five piles.
Why is The week $7,500?
Because the seven-day job includes the connections done properly, monitoring after it is live, a plan for what to automate next, a knowledge store if the work needs one, and thirty days of support. That is the package most people book.
When do I need $15,000+?
When two or more processes have to live together, the integrations go deeper, and someone has to own the architecture. If the second workflow shares nothing with the first, it is not a discount bundle. It is more work.
Can I start at $5,000 and upgrade?
Yes. That is often the honest path. Ship one process. See if realized ROI shows up. Then talk about The week extras or a second workflow. Do not pre-buy a program you cannot staff.
Which plan should a CFO approve first?
The one that matches a written process with a named owner. If you cannot write the steps, do not buy Several workflows. Buy a conversation, or buy One workflow after we map it.
Written by
Tobiloba Odejinmi
Head of Engineering at 10mg Health. I have run engineering at Zeeh Africa and sold Insurpass and Shopl. I still write the code. If you have one process that still runs on people copying things, we can look at it in thirty minutes.
