Ground · internal only
We exist to create software that brings peace of mind. The mantra trains the message. It is not the pitch. Do not cite it in buyer-facing language.
People feel that the software understands the work, that they remain in control, and that they can move forward with peace of mind.
Mantra
Five tests the message still has to pass.
Wonder is the quality of attention on their work. Simplicity removes a burden. The person comes before the problem. The software carries weight and they keep control. Courage makes the difference dependable.
01
Work with Wonder
Test — Did we give the right thing our full attention, discover a better question, and turn what we learned into service?
02
Make Complexity Feel Simple
Test — Did we remove effort, uncertainty, or a decision that the person should never have had to carry?
03
Meet the Person Before the Problem
Test — Does the person feel understood, respected, and free to make a confident choice?
04
Learn the Work, Lighten the Work
Test — Is the system doing more of the work while the person retains understanding and control?
05
Build with Courage, Earn Peace of Mind
Test — Have we made life meaningfully better in a way people can see, trust, and safely use?
Axioms
Describe their situation so precisely that replying is easier than ignoring.
Meet the person in the week they are already in. Offer a calmer next state. You are absent from the message.
Not about you
No features, benefits, or logo slide. Leading with the solution admits you understand the product and not the week they are in.
One insight
Two to five sources may sit behind the note. The note carries one number, place, or deadline. The hard thinking stays with the writer.
Value, then ask
One to three sentences. The ask is small and comes after the fact. Sometimes there is no ask. Refusal stays safe.
Jobs
The job changes what you hand them. The voice stays.
Name the condition before the sentence. Four jobs, one person.
PQS
Situation
You can prove the week they are in. You cannot hand them a next action they can take today.
Recognition. One checkable fact. The product stays out.
The planner re-enters the same order on three screens before the floor sees it.
Leave out — The product, the research, and any second insight.
PVP
Gift
Two to five sources combine into something they can use today, even if they never buy.
A path they can walk without you. The product appears only if it shortens that path.
The schedule says this batch finishes at 2. The floor log still has it open at 4. Here is the one field that would have shown that.
Leave out — The whole file. The product, unless it shortens a path they can already walk.
Pre-written
Condition
A named trigger is already true: a job change, a funnel state, a person who moved.
The condition as a fact, then one consequence that is true because of it.
The production supervisor posting went up Monday. It asks for someone who can reconcile the schedule with the floor.
Leave out — A model choosing, at send time, which of forty facts matters.
Stolen answer
Asymmetry
You hold something they would take if they could: a pattern in your data, a negotiation, a failure the last buyers already paid for.
The answer, complete. The data is the demonstration.
Here is the step plants in this position still do by hand after the system says the order is finished.
Leave out — A dashboard, and any claim that the product is better.
Each email
Six steps are the order. The body stays short.
A step this job cannot evidence is omitted and named in a sender note. A correct order that reads like a brochure has still failed.
01
Reality
Buyer's narrative + observable artifact + seller's model → buyer confirms.
Open on the scene of the current opposite. Location + artifact. Invite "that's right."
02
Problem hypothesis
Operational mismatch + evidence requirement + confirmation question + status (inferred, call_confirmed, or artifact_verified).
Name the elephant as a tentative hypothesis. Never as a customer fact.
03
Impact hypothesis
Quantified loss, risk, constraint, or clearly labeled hypothesis.
Stakes as a scene of consequence, not a slogan. Label confidence.
04
Mechanism
One capability, classified Native, Configured (Builder), Integrated, or Roadmap. Logic Pilot is an action inside a class, not a fifth class.
Therefore, not and-then. Use one capability that makes the moment possible. Classify it. They keep understanding and control.
05
Proof
Customer-data demo, live build, benchmark, or comparable reference.
One comparable person's five-second moment. The buyer remains the protagonist.
06
Choice
Explicit, low-pressure next step.
Make refusal safe. The story does not close itself.
How to write
The condition is science. The sentence is still written by hand.
01
Condition
Name the circumstance that makes this note justified, before the sentence.
Stop — You cannot name it. More context will not name it for you.
02
Last line first
Write the one sentence they would be glad to have read. Then find the facts that make it true.
Stop — The sentence is a claim about you.
03
Breathe
Expand across two to five sources. Contract to one insight.
Stop — The note explains how you found it.
04
Kills
Run the tests below. Fix the first failure.
Stop — Any test fails.
05
Compress
Preview in the first 120 characters. One insight. Ask small, or do not ask.
Stop — It is longer than three sentences.
06
Reader pass
Read it as the person in the situation. Then show it to one human who lives that week.
Stop — They would not keep it.
07
Ten by hand
Write ten before any system writes one. A clumsy note that still gets replies means the situation is real. Then raise the bar.
Stop — You are editing a model’s email instead of examples.
Kills
A draft dies on the first failure.
Main character
Meet the person before the problem.
The sentence is about you, a feature, a benefit, or a logo.
Delete your name and the sentence still stands.
Specific
Give the right fact your full attention.
A different company could receive the same sentence with the name swapped.
A name, a record, and a number that only fit this company.
Costume
Remove a burden. Leave them the path.
Remove the product and the gift is worthless.
They can use it today and never reply.
How, not so-what
Complexity stays with the writer.
You narrate the research, the model, or the filters.
One number, place, date, or name. Nothing about the method.
Expert
Respect the person who already carries this.
The reader already has a working way through this, and the note ignores it.
The burden is still theirs, and the note does not shame the way they cope.
Belief
Tell the truth about uncertainty.
The note assumes they trust your conclusion.
If you compare paths, you name the options and the tradeoff.
Channels
The same sentence, thinner by room.
Preview, then the insight, then a small ask or none. The preview is a place or a thing they own.
“The same order is open on the planning screen and the floor sheet.”
Call
Open on the insight. The first sentence is the scene.
“Is the batch still open on the floor after the schedule says it finished?”
Social
The same fact, framed as news they can use. The product stays out of the first line.
“The schedule and the floor log disagree on the same order.”
The send gap is pacing, not a deadline. A reply ends the sequence.