Claude buildout · 14 days
We build the Claude workspace your team actually uses.
Your team already has Claude. Most of them open it, look at an empty box, paste in something half-formed, and go back to doing the job by hand. We build the layer that fixes that: your context, your processes, your tools, wired in — so the same work comes out the same way regardless of who asked. It is the setup we run our own company on.
$7,500
Fixed price · 14 days · 5 workflows built
Fixed scope and fixed price, agreed before we start. If the discovery call tells us your team would not get $7,500 of value out of this, we will say so on the call.
The problem
The problem was never Claude. It is the blank page it hands every person, every morning.
Rolling out licences is not a rollout. Without a shared setup underneath it, every person quietly invents their own way of working, and most of them give up somewhere in the first fortnight.
- 01
Everyone starts from zero
Each session begins with no memory of your business. Your people spend the first ten minutes re-explaining who you are and how you do things, then rush the actual request.
- 02
Same task, five different answers
Five people run the same recurring job and get five different formats, five different tones, five different standards. Nothing is repeatable, so nothing can be trusted downstream.
- 03
The good prompt disappears
Someone eventually works out how to do it properly. That prompt lives in their history, or a note, or their head. Nobody else ever sees it, and it leaves when they do.
- 04
It never touches your real tools
Without integrations, every task is a copy-paste round trip between Claude and the systems where the work actually lives. The tax on that is where the promised time saving quietly goes.
The buildout
A configured workspace, built and handed over.
Eight components. Built inside your workspace, on your data, and yours to keep and change after we leave. Nothing here is locked to us.
- //01
Workspace & project structure
Projects laid out around how your team is actually organised, so people land in the right place instead of one shared everything-drawer.
- //02
Business context library
Who you are, what you sell, how you speak, what good looks like, what is off-limits. Written once, loaded automatically, so nobody re-explains the company again.
- //03
SOPs packaged as Skills
Your recurring processes turned into repeatable Skills your team invokes by name. The same steps, the same output format, every single time.
- //04
Connected tools
Claude wired into the systems where your work lives through MCP, so it reads and acts on real data instead of whatever someone remembered to paste in.
- //05
State files & trackers
Living documents that hold the current state of ongoing work, so a session picks up where the last one stopped rather than starting cold.
- //06
Decision frameworks
The judgment calls your team makes repeatedly, written down as explicit criteria — so the reasoning is consistent and reviewable, not improvised per person.
- //07
Review & maintenance protocol
A standing routine for keeping context current as the business changes. Setups rot; this is what stops yours going stale by month three.
- //08
Handover, export & backup
Documentation your team can actually follow, plus export and backup routines. You own the whole thing outright when we finish.
How it works · 14-day build
Seven phases, fourteen days, and a workspace your team owns at the end.
Fixed sequence, fixed timeline. You will know what is happening on any given day before we start.
- //01Days 1–2
Discovery
We find the five workflows worth building.
Sessions with the people doing the work. We map what recurs, what it costs in hours, and which five jobs earn their place in the build. You approve the list before anything gets built.
- //02Days 3–4
Workspace architecture
The structure everything else sits inside.
Projects, permissions, and naming laid out around your teams and their work, designed so it still makes sense once you have added things we never saw.
- //03Days 5–7
Context build
Your business, written down where Claude can read it.
We build the knowledge layer: positioning, terminology, standards, constraints, and the reference material each workflow depends on. This is the phase that does most of the work.
- //04Days 8–9
Tool integration
Claude connected to the systems you already run.
MCP connections into your real stack, scoped to what each project legitimately needs. Read access where reading is enough, write access only where you have asked for it.
- //05Days 10–11
Workflow packaging
Five workflows, running the same way every time.
The five approved jobs built as Skills, then tested against real cases from your own backlog rather than tidy examples we made up.
- //06Days 12–13
Team training
Your people using it without us in the room.
Live sessions on the workspace as built, not generic prompt training. People run their own real work through it while we are still there to correct things.
- //07Day 14
Handover
Documentation, ownership, and a 30-day line to us.
You get the written setup, the maintenance protocol, and everything transferred to your ownership. We stay reachable for 30 days for the questions that only surface in week three.
Pricing
One package. One price.
No tiers to compare and no discovery phase that quietly bills by the hour. This is the whole thing.
$7,500
Fixed · 14 days · Paid 50% up front, 50% on handover
If you want more
- Each additional workflow
- $1,000
- Ongoing maintenance & new workflows
- $750/mo
Optional, never bundled in by default, and you can decide on either of them after handover rather than now.
- Discovery sessions with your team
- Full workspace and project architecture
- Business context library, written and loaded
- Five workflows built and packaged as Skills
- Tool integrations via MCP
- State files, trackers, and decision frameworks
- Live team training on the workspace as built
- Documentation, export routines, and full ownership
- 30 days of support after handover
The difference
Before, and after.
Today
- Every session starts by re-explaining the business
- The same job comes back in a different shape each time
- One person is unusually good at it and nobody knows why
- Constant copy-paste between Claude and your real systems
- Licences bought, mostly unused by week three
After handover
- Context is already loaded before anyone types anything
- Recurring work comes out in the same shape every time
- The best way of doing it is written down and shared
- Claude reads and acts inside the tools you already run
- A workspace your team opens because it is faster than not
Why us
We are not configuring something we have only read about.
Most people selling this are selling a setup they have never had to depend on. We built ours first, for ourselves, and we still run on it every day.
We run our own company inside this. Our intake, delivery, and reporting all sit on the same structure we would build for you: Skills for recurring work, MCP into our own tools, context files that keep the three of us consistent. We know which parts hold up under real use because we are the ones using them.
We have already hit the failure modes. Context that goes stale. Skills written so tightly they break on the first real edge case. Integrations scoped so broadly they make everyone nervous. We found those on our own time, on our own work, which is why they are not going to be discovered on yours.
A prompt pack teaches one person a trick. This builds something the whole team works inside. The difference shows up in month two, when the person who was good at prompting is on leave and the work still comes out right.
You own it, completely. Everything is built in your workspace, documented in plain language, and transferred to you at handover. There is no seat we hold, no platform of ours in the middle, and nothing that stops working if you never speak to us again.
We will tell you if you are not ready. If your recurring work is not actually recurring, or the processes are still changing weekly, this is the wrong thing to buy right now. You will hear that on the discovery call, not after the invoice.
FAQ
Fair questions.
Do we need Claude licences already?
Yes. This is a buildout on top of your team's existing Claude Team or Enterprise plan, not a reseller arrangement. If you have not chosen a plan yet, we will tell you on the discovery call which one your use case needs, and we make nothing either way.
What if we do not have five workflows worth building?
Then you should not buy this yet, and we will say so on the call. The package is priced around five because that is roughly where a workspace stops being a collection of tricks and starts being a system. With two or three, you would be paying for structure you do not need.
Is our data used to train models?
No. The buildout runs inside your own workspace under your plan's terms, and we work under whatever confidentiality agreement you want in place before we start. We do not move your data anywhere else and we do not keep a copy after handover.
What happens after the 30 days of support?
Most teams carry on unaided, which is the intended outcome. You own the documentation and the maintenance protocol, so nothing depends on us. If you would rather we kept extending it and adding workflows, the monthly option is there, but it is genuinely optional.
Fourteen days seems fast. Is it real?
It is fourteen calendar days, and it holds because the scope is fixed on day two and does not move. The part that needs your people is concentrated in discovery and training. The rest is our build time. Where projects like this slip, it is almost always scope creep rather than the work itself.
You are a new company. Why should we trust this?
Fair. We do not have a decade of logos to point at, and we are not going to pretend otherwise. What we do have is the same system running our own operations, a fixed price so your exposure is known up front, and a discovery call whose entire purpose is telling you honestly whether this is worth buying. Judge it on that call.
Next step
Thirty minutes to find out if this is worth building.
Bring the recurring work your team keeps redoing by hand. We will tell you what a workspace would take that off them, and whether the five workflows are actually there.