Documents, answered
The questions businesses ask about business documents, answered the way we answer them on a call.
A document is a decision tool, not a brochure. Write it once, in a structure somebody can act on, keep it where the next person will find it, and reuse it rather than rebuilding it every quarter from memory.
Questions we get
Questions about proposals, SOPs and the documents a business issues over and over.
Our proposals take hours and still look inconsistent. Fixable?
Yes, and usually quickly. The cause is almost always that every proposal starts from the last one somebody could find, so each is a slightly mutated copy of a document nobody has reviewed in two years.
What should a business proposal include?
Their situation in their own words, one clear recommendation, proof standing beside every claim, the price stated plainly with inclusions and exclusions, and exactly one next step with a date.
What is an SOP and do we need them?
A standard operating procedure is a short written description of how a recurring task runs: the trigger, the steps, the owner, what done looks like, and what to do when the exception appears.
Can you clean up documents we already have?
Yes, and that is usually faster than starting over. Most businesses have the content already, scattered across versions, with no agreement on which is current.
Are the contracts you draft legally binding?
Documents are prepared as operational templates, and anything with legal consequence should be reviewed by qualified counsel before you rely on it. We are practitioners, not lawyers.
How fast can documents turn around?
A single template is usually days. A full set covering proposals, statements of work, contractor terms and the core SOPs is typically a matter of weeks depending on how much source material exists.
Will our documents still sound like us?
Yes, because the language is pulled from how you already write and speak, taken from your existing emails, proposals and calls rather than invented.
How do we stop SOPs going stale?
Put a review date and a named owner on each one, and review them on a schedule rather than when someone notices they are wrong.
Who should write our SOPs, us or you?
Best results usually come from watching your team do the work and writing it up, then having them correct it. People are far better at fixing a draft than producing one from nothing.
Can this be handed to a new hire?
That is the point of it. The test we use throughout is whether someone competent but new could run the task from what is written, on their second day, without interrupting anyone.
Your situation is specific. Write to hello@shaheer.io and get the specific answer within one business day.
Read next
The service itself, the working guide, and the questions we get on adjacent work.
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built
