Inquiries
4.15 per workdayGrowth that closes the loop.
Start with the revenue target. Work backward to daily controllable inputs, identify the current constraint, run one bounded experiment, and preserve the result as operating evidence.
A model, an offer, and owned workflows.
The useful patterns are familiar: respond quickly, make a specific offer, work the leads, remove one constraint, and measure customer economics. Obtuse Work connects them to the actual operating record and adds the controls most growth advice leaves out.
Qualified
1.45 per workdayConversations
1.00 per workdayAccepted sales
0.25 per workdayConfigured assumptions create the plan. Only imported records and closure receipts create actual results.
Name the operator, business shape, and situation the system is designed to serve.
Describe the expensive operating pressure in observable language.
Promise a measurable change the delivery system can actually produce.
Attach only source-backed results, exact receipts, and the measurement window.
Make scope, owner, first value, and acceptance conditions explicit.
State what requires approval, what stops the system, and what happens when assumptions fail.
01Instant intake and response+
TriggerAn owned website inquiry or scoped connector signal arrives.
- Preserve attribution
- Build a qualification brief
- Draft the next move
- Start the response clock
Human gateA person approves external outreach and every commercial promise.
Closure receiptLead, attribution, response event, owner, and elapsed time.
02Grounded lead context+
TriggerA lead passes identity and consent checks.
- Inspect approved sources
- Separate facts from questions
- Record freshness
- Draft discovery questions
Human gateA person decides whether the context is relevant enough to use.
Closure receiptSource references, retrieval time, confidence, and accepted questions.
03Voice qualification and handoff+
TriggerAn opted-in caller arrives or an operator approves a callback.
- Disclose automation
- Capture the need
- Check availability
- Escalate consequential requests
Human gateA person owns outbound calls, binding terms, and escalated cases.
Closure receiptConsent, transcript hash, structured outcome, escalation, and follow-up.
04Dormant pipeline reactivation+
TriggerA qualified lead has no recent action and no closeout receipt.
- Select a narrow segment
- Draft a useful follow-up
- Stage a bounded sequence
- Stop on outcome
Human gateA person approves the audience, content, channel, and release.
Closure receiptDelivery, reply, opt-out, booking, and terminal-state receipts.
05Accepted-sale onboarding+
TriggerAn accepted quote or invoice joins a customer journey.
- Copy accepted scope
- Assign the owner
- Stage first value
- Track delivery and continuity
Human gateA person approves scope changes, dates, money, and customer messages.
Closure receiptAccepted scope, owner, first value, delivery proof, and closeout.
06Evidence-led content+
TriggerA verified operating insight is approved for public use.
- Extract the bounded claim
- Draft channel variants
- Review voice and rights
- Publish and attribute
Human gateA person approves every public claim and publishing action.
Closure receiptSource, revision, approval, publication URL, and attributed outcome.
Speed with context
Intake starts the clock, but the system prepares a grounded brief before anyone reaches out.
One constraint
The engine compares the configured model to observed journey evidence and points to one next move.
Money through delivery
A sale is not the finish line. Payment, accepted delivery, continuity, and referral remain one journey.
Autonomy with receipts
Automation prepares and coordinates; people retain consequence, and every terminal state needs evidence.
Make growth an operating system.
Bring the current offer, sales path, or delivery bottleneck. We will map the loop and configure the first measurable motion.