Straight answers to common questions.
Everything worth knowing before you reach out — what we build, how we work, what it asks of your team, and what happens after we hand the system over. If your question isn't here, ask it directly, and we'll answer the same way we've answered these: plainly.
What we build, and how long it takes.
The two systems, who they're for, and the shape of an engagement. For the full breakdown of what's inside each, see the Services page. And if you're weighing this against what you've already heard, we've written up the three things people get wrong about operating systems.
What's the difference between Content OS and Business OS?
Content OS turns what you know into a publishing engine — knowledge organized, strategy set, workflows built, and your team trained to create consistently without you. Business OS does the same for how your company runs — documented processes, clear roles, a connected tool stack, and decisions that no longer bottleneck on one person. Most engagements start with one and add the other later.
How long does it take to build an Operating System?
Content OS typically takes 8 to 12 weeks from kickoff to handoff, and Business OS 10 to 14 weeks. Each extension — a website, a CRM integration, an automation — adds 2 to 4 weeks. The range depends on how complex your business is and how much existing material we work from. You get a specific timeline after discovery, once we both know exactly what we're building.
What size and kind of business do you work with?
Founder-led businesses, from solo operators to teams of fifty or more. Size matters less than maturity: you need genuine expertise and enough operating history that there's real knowledge worth organizing. Very early, pre-product-market-fit startups usually aren't a fit yet — the knowledge a system would capture is still forming. If that's you, our Knowledge Hub will serve you better than an engagement for now.
Can we start small and expand later?
Yes, and many do. A focused first project — a knowledge audit, a content strategy, a single workflow — is a natural way to begin. We design every component to be extensible, so a small start becomes part of a full Operating System later without tearing anything out and rebuilding. We'll help you scope what makes sense for where you are now.
How is this different from hiring an agency or a consultant?
An agency produces the work for you; when you stop paying, the work stops. A consultant hands you advice and leaves the implementation to you. We build a system you own and operate — and we train your team to run it without us. The difference is ownership. When we're done, the capability stays in your business instead of walking out the door.
How we actually work together.
What an engagement asks of you, how we handle your tools, and the way we run the build day to day.
How much of our team's time will this take?
Discovery asks the most — roughly 3 to 5 hours a week from the people who hold the knowledge, because that's what we build from. During the build phases it drops to 1 to 2 hours a week for review and feedback. We do the heavy lifting; we just need your expertise at the right moments. We work around your team's existing commitments, not on top of them.
Do we have to switch tools, or can you work with what we already use?
We start with what you have. Discovery includes an audit of your current stack, and we build on whatever's working. We only recommend replacing a tool when there's a clear reason — redundancy, poor fit, or a gap it can't bridge. The system design comes first; the tools follow from it. We're tool-agnostic on purpose, so you're never locked into a choice that doesn't serve the work.
What do you build automations with?
Our core tools are Claude Code for custom AI workflows and n8n for multi-step automations, with Zapier and Make.com when they're the better fit. But the tool is the last decision, not the first — we choose it around your infrastructure, your team's comfort, and what the system actually needs to do.
Do you work remotely, and does our time zone matter?
We work remotely by default, and our process is built for it — asynchronous progress with regular synchronous check-ins. Discovery interviews happen over video; the build runs on shared documents and scheduled reviews. Time zone isn't a barrier: we set meeting times around your team's hours. If on-site time would genuinely help your engagement, we'll talk it through.
After the build, and how to begin.
What ownership actually means once we hand over, how we handle the unexpected, and what the first step looks like.
What happens after you hand the system over?
You own and run it — completely. Every engagement includes a 30 to 60 day support window after handoff, where we answer questions, fix snags, and help your team build confidence. After that, it's your call: keep an ongoing support arrangement, book occasional strategy sessions to refine the system, or run it entirely on your own. There's no required retainer. Independence is the whole point.
What if the scope changes partway through?
We handle it in the open. If something we uncover during the build changes the scope, we bring it to you right away with clear options and a revised plan before any work continues. Small adjustments we usually absorb; significant ones we agree on together first. No surprises, and nothing gets quietly added or dropped.
What if we're not sure exactly what we need?
That's normal, and it's what discovery is for. Plenty of businesses arrive knowing something needs to change without being able to name it. We ask questions, study how you work today, and surface the highest-impact opportunities. By the end of discovery we both have a clear, shared picture of what to build — and you're free to stop there if the scope isn't right.
How do we get started?
It begins with one conversation — no commitment. If there's a fit, we write a proposal built around your specific situation. Approve it, and we schedule a kickoff to align on scope, timeline, and involvement, then move into discovery with interviews and a current-state audit. If there isn't a fit, we'll tell you honestly. Either way you'll leave with a clearer view of your systems. The Contact page is where it starts.
Didn't find your answer?
Ask it directly. Put a time in the calendar and we'll answer it the same way we've answered everything here — plainly, and in our own words. If we can't give you a straight answer, we'll say so.
Ask Your Question