Skip to content
DuranteDurante
ALL SYSTEMSGet Access →

Durante OS / Use Cases

005 / WORK · NOT DEMOS

Six shapes. Real work.

These are not features. They’re situations operators bring to us, traced end-to-end through the algorithm. Same seven phases. Different tone, different packs, different stakes — same chain of receipts.

006 / BROWSE BY SHAPE
RECEIVABLES
Recover stuck invoices
147 runs · cycle 2h 49mINBOX
Triage and answer
1,204 runs · cycle 90 secPRODUCT
Ship one feature
241 runs · cycle 4dSALES
Account warmth
608 runs · cycle 18hBOARD
Quarterly brief
56 runs · cycle 6hVENDORS
Renewals & contracts
88 runs · cycle 3d+
Custom shape
Bring yours · 30 minREF
The pack library
14 packs · phase-filterable
CASE 01RECEIVABLES

“Our A/R aging is full of quiet 40-day-olds.”

— CFO, $14M ARR services firm. Six accounts overdue. None hostile. All stuck. The team has stopped chasing because it feels relationship-corrosive.

The pain ▸
  • Late invoices read as "the customer is upset" — but most are procedural
  • Manual follow-up is tone-fragile; SDRs ghost-write the CFO's voice
  • Board call referenced cash; the spreadsheet is older than the situation

Run 0241 · live traceSHA · 0241ff

OBS08:1447 signals → 3 named. Acme top of stack · 0.91 confidence · $12,400
THINK08:213-model debate · hypothesis “ERP cutover broke A/P” · 0.78 consensus
PLAN08:344-step plan · 2 reversible · operator approves in 4 min
BUILD08:413 artifacts staged · voice-matched email · re-issued invoice · calendar block
EXEC08:43SMTP 250 · 0 retries · all side-effects bracketed
VER09:48Reply received · tone positive · hypothesis confirmed
LEARN11:08Pattern named · doctrine 0.0.7 → 0.0.8 · auto-playbook seeded
2h 49mcycle
$12,400 cleared · relationship preserved · 22h faster than predicted
PACK · 06 vendor recoveryPACK · 07 brand intelligencePACK · 09 compliance loop
CASE 02INBOX

“My inbox is the org chart, and it’s on fire.”

— Founder, Series A SaaS. 200+ inbound threads a week. Three a day actually need her. The other 197 metabolize into anxiety.

The pain ▸
  • Auto-replies erode trust; sorting rules don't understand stakes
  • "Important" is a context call, not a keyword — only humans know
  • EA drafts read like a 23-year-old, not the founder

Run 0312 · morning sweepSHA · 03127a

OBS07:00214 threads · 3 escalated · 11 drafted · 200 archived with note
THINK07:02Each escalation gets a one-line stakes summary + recommended tone
PLAN07:0311 drafts · voice-matched · gated · awaiting approval
BUILD07:03Drafts written in founder voice file v2.1· zero “I hope this finds you well”
EXEC08:309 sent by founder one-click · 2 revised · all chain-receipted
VER+24hReply rate 62% · sentiment positive · 1 retry triggered
LEARNweekly"Procurement question" pattern surfaced · routed to operator pre-draft
90sec
From inbox-open to 3 named situations · 197 threads handled with one approval gesture
PACK · 02 inbox triagePACK · 07 brand intelligencePACK · 11 sales intelligence
CASE 03PRODUCT

“Shipping one feature takes four weeks of coordination.”

— Head of Product. PRD → eng review → design → QA → release notes → support brief. Each handoff is a fresh tax. Nothing is parallel.

The pain ▸
  • Each artifact has a different author and tone; the customer feels the seams
  • Release notes are written last and read first — by the very people the feature is for
  • QA finds drift between PRD and built; nobody owns the reconciliation

Run 0177 · feature pipelineSHA · 01775c

OBSD-0Idea: smart filter v2. Pulls top-12 customer asks · last 90 days
THINKD-03-model architecture review · 1 dissent surfaced · resolved in PRD
PLAND-1PRD + eng plan + QA plan + comms plan · same chain · co-signed
BUILDD-1→3Claude Code lands diff · release notes drafted · support brief drafted
EXECD-4Ship · post · notify · update help-center · all bracketed
VERD-4 → D-117-day metric watch · adoption +34% on target segment · no drift
LEARND-14"Asked-for filter" pattern reinforced · new threshold for direct-build
4dcycle
From idea to lived-feature · 7× compression on the prior cadence · one chain, six artifacts
PACK · 05 feature pipelinePACK · 03 architecture guardianPACK · 08 deck composer
CASE 04SALES

“Pipeline reports tell me what happened, not what’s drifting.”

— VP Sales. CRM is current. Forecast is theatre. The 11 deals that quietly went cold last week are still in the spreadsheet as "committed."

The pain ▸
  • Sequence tools spray-and-pray; account warmth degrades silently
  • Reps "update Salesforce" — meaning they don't, until forecast Friday
  • The CEO finds out a strategic account ghosted in week 3 of week 8

Run 0419 · account warmthSHA · 04192f

OBSM-W-FWatches every named account · email lag, CRM drift, news, churn-shape
THINKlivePer account: temperature 0–1 · drift vector · hypothesis if < 0.5
PLANliveSuggests one move per cooling account · rate-limited per rep
BUILDliveDrafts a voice-matched touch — never sequence-spam · always anchored to signal
EXECrepRep one-clicks · operator logs · CRM auto-syncs the chain
VER+72hDid warmth recover? · 71% yes · drift on the others escalated
LEARNmonthlyPer-rep · per-segment what's working — by signal, not vibe
+22% close
On strategic accounts under operator watch · zero increase in rep workload · forecast finally matches reality
PACK · 10 sales outreachPACK · 11 sales intelligencePACK · 12 outcome audit
CASE 05BOARD

“The board deck eats six days of executive time.”

— CEO, Series B. Five execs assemble 60 slides quarterly. Half the slides are last quarter, re-titled. Nobody reads ahead. Everybody re-asks the same questions.

The pain ▸
  • Each function copies last quarter's template and edits numbers — context dies
  • "What changed?" is the question of the meeting; the deck doesn't answer it
  • The actual update is 12 slides; the other 48 are defensive

Run 0093 · Q2 board briefSHA · 0093e1

OBSQ-14dPulls every receipt-of-record since last brief · 4,217 receipts indexed
THINKQ-12dThree deltas surfaced · two wins, one drift · CEO co-signs the framing
PLANQ-10d12-slide outline · one slide per delta · every claim chained to a receipt
BUILDQ-7dComposer drafts · execs review their own slide · 30 min each, not 6 hours
EXECQ-2dDistributed 48h pre-meeting · read-ahead receipts confirm 9 of 9 directors opened
VERQ+1dDirector questions logged · 4 follow-ups assigned with chains
LEARNQ+7d"Two wins / one drift" template reinforced · seeded for Q3
6hcycle
Down from 6 days of executive time · directors read ahead · meeting becomes a decision, not a recap
PACK · 04 strategy briefPACK · 08 deck composerPACK · 12 outcome audit
CASE 06VENDORS

“Renewals auto-renew on us at 18% bumps.”

— Ops, 80-person company. 47 SaaS vendors. The renewal email arrives 7 days out. Nobody owns the negotiation. Everybody owns the regret.

The pain ▸
  • Renewal terms hide in PDFs that nobody re-reads at signing
  • Usage data lives in the vendor's dashboard, never normalized
  • The team finds out at invoice time that the bump landed

Run 0508 · vendor renewalsSHA · 0508aa

OBST-90dWatches contract calendar · flags every renewal 90 days out, not 7
THINKT-85dUsage vs price vs alternative · "fair-floor" benchmark from prior negotiations
PLANT-80dThree negotiation paths · keep / cut / replace · operator picks one
BUILDT-70dNegotiation email drafted with usage receipts attached · tone: matter-of-fact
EXECT-60dSent · logged · counter-offer received in 4 of 5 cases · chained
VERT-30dRenewal signed at 0–4% bump vs the original 18% ask · saved $84k/yr
LEARNpostPer-vendor pricing graph updated · feeds next renewal's "fair-floor"
$84k/yr
Saved across 12 renewals · zero relationships damaged · contracts re-read 90 days early instead of 7
PACK · 06 vendor recoveryPACK · 09 compliance loopPACK · 13 doctrine update
CLOSE / SAME ALGORITHM · SIX SHAPES · ONE CHAIN

Your shape is probably in here. Bring it anyway.

30-minute office hours · we trace one stuck workflow through the algorithm with you · output is a named pack + first-run receipts you can keep.