Employee question
An employee asks how something works. Instead of answering the same thing over and over, capture it as an SOP, policy, checklist, or guide.
New book coming soon
Only Answer Once
Build your business systems one question at a time.
Most business owners know they should document their processes and get knowledge out of their heads.
The hard part is knowing where to start.
A practical way to build systems as you work. Only Answer Once helps business owners create a culture where knowledge is captured, organized and reused instead of repeatedly recreated.
Get updates about the book
The book is currently being written. No preorder or payment. Just occasional updates as it gets closer to release.
The starting point
You already know you need systems.
Business books, consultants and gurus have been saying it for years:
- Document your processes.
- Build SOPs.
- Systemize the business.
- Get the business out of your head.
They are not wrong.
But those are enormous instructions.
Where do you start? Which process comes first? What actually deserves documentation? How are you supposed to document an entire business while also trying to run it?
Only Answer Once starts somewhere much smaller.
Start with the next question.
A small action. A lasting answer.
The idea is simple.
Someone asks you how something works. You answer them.
If that answer matters beyond that one conversation, capture it.
Now the next employee does not need to ask you. The next customer can find the answer. Future-you does not have to solve the same problem again.
- Question
- Answer
- Document
- Reuse
- System
- Culture
Customer question
A customer asks a recurring question. Instead of repeating yourself individually every time, turn the answer into an article, FAQ, or reusable response.
Solved problem
You solve a problem or figure something out you will likely need again. Instead of rediscovering it next time, save it as a note, how-to, or troubleshooting guide.
An everyday practice
Systems should not be a project. They should be a habit.
Most businesses treat documentation like something they will eventually get around to.
A giant SOP project. A process-mapping exercise. A future initiative that never quite happens.
Only Answer Once approaches it differently.
Every question, recurring problem, clarified expectation, and repeatable decision becomes an opportunity to make the business slightly less dependent on memory.
You do not stop running the business to build the system.
You build the system while running the business.
- Has this already been answered?
- Should we write this down?
- Will someone need this again?
- Where should this answer live?
This is not a book about writing more SOPs.
An SOP might be the right answer. But sometimes the right answer is:
- a checklist
- a policy
- a decision rule
- a template
- a customer-facing article
- a troubleshooting note
- a standard way of naming files
- a reusable AI prompt
The goal is not more documentation for the sake of documentation.
The goal is to stop useful knowledge from disappearing.
The compounding benefit
One answer does not change a business. Thousands of captured answers do.
- Less knowledge trapped in the owner’s head
- Fewer repeated interruptions
- More consistent answers across the team
- Easier delegation
- Better onboarding
- Clearer standards
- Better preparedness for automation and AI
- A business that gradually develops a memory of its own
Before you can automate what your business knows, your business has to know what it knows.
Inside the book
Only Answer Once will show you how to:
Know what to capture
Recognize questions, decisions, and solutions worth preserving.
Capture knowledge while you work
Document without turning documentation into a second full-time job.
Put answers where people can find them
Because information is not useful if nobody knows where it lives.
Build the “look first” habit
Create a culture where the team checks existing knowledge before starting from zero.
Turn answers into systems
Move from isolated documents toward repeatable ways of operating.
Prepare your business for delegation, automation, and AI
Build the documented knowledge those things depend on.
A note from the author
Why I’m writing Only Answer Once
Too many businesses have knowledge sitting in people’s heads.
Questions get answered repeatedly. Problems get solved and forgotten. Processes technically exist, but nobody can find them. Owners are told they “need systems” without being given a practical way to start building them.
Only Answer Once is my attempt to make systemization practical enough that a business can start today.
Only Answer Once
Start with the next question.
Only Answer Once is currently being written.
If the idea resonates with you, sign up and I’ll let you know as the book develops and when it is ready.
Get book updates
No preorder. No payment. Just occasional updates.
