Our work / Field notes
01 first-party project 20 worked examples
See how the
work gets done.
Our own software and worked examples of the problems we help solve. Explore the decisions, the handoffs, and what happens when something goes wrong.
Explore the collection01 / First-party work
Built for our own business.
A real application. Features checked against its source, with the limits of that evidence stated.
Conceptual cover · source-based storyBillable
Time is simple.
Billing rules aren’t.
Our own application connects time entries, retainer periods and invoice preparation. The useful detail is how it keeps hours worked separate from hours ready to bill.
02 / Worked examples
Recognize the problem?
Follow the decisions.
These are fictional operating scenarios and proposed solutions. They demonstrate our approach, with no invented clients or measured results.
20 of 20 worked examples
Worked exampleRevenue & CRM
Customer success: turn account signals into a clear next action
Find the accounts that need attention, understand the warning signs, and choose the next action.
Explore the proposed workflow
Worked exampleRevenue & CRM
Candidate search: understand every match on the shortlist
Turn a recruiter brief into a shortlist with a visible reason for every match and every gap.
Explore the proposed workflow
Worked exampleFinance & delivery
Commission dashboard: trace the payout back to the deal
Give reps a clear earnings view and finance a reviewable path from deal credit to payout.
Explore the proposed workflow
Worked exampleRevenue & CRM
Automated Scoping Agent: turn a scattered brief into a reviewable proposal
Carry a scope brief into an estimate, a proposal, and a coordinated sales handoff.
Explore the proposed workflow
Worked exampleRevenue & CRM
Partner portal: connect learning, referrals, and deal registration
Bring partner learning, referrals, deal registration, and quoting into one connected experience.
Explore the proposed workflow
Worked exampleFinance & delivery
Consultant portfolio: see stalled work across delivery tools
See project health, stalled work, and the next useful action across your delivery tools.
Explore the proposed workflow
Worked exampleRevenue & CRM
From scattered account notes to a five-minute call brief
A proposed agent brings meeting context into a private brief before a sales call. Follow the matching, source checks, and delivery rules that make the brief useful.
Explore the proposed workflow
Worked exampleRevenue & CRM
A product-qualified lead needs an account and an owner
Connect usage signals to a known account and give sales the evidence behind an alert. Keep billing state separate from product interest.
Explore the proposed workflow
Worked exampleApprovals & review
Prior authorization: assemble the packet, preserve the judgment
A proposed administrative workflow for missing documents, submission acknowledgments and status follow-up. Payer decisions and clinical judgment remain explicit boundaries.
Explore the proposed workflow
Worked exampleFinance & delivery
Turn a signed scope into a reviewable billing schedule
Connect contract terms to delivery milestones and invoice drafts. Keep changed scope, client acceptance and invoice release visible.
Explore the proposed workflow
Worked exampleRevenue & CRM
Route the lead without replacing the account owner
Define owner precedence before adding round robin. Existing customers, ambiguous account matches and unavailable reps need different paths.
Explore the proposed workflow
Worked exampleRevenue & CRM
Prove a CRM migration before you cut over
A successful import can still lose owners and relationships. Reconcile identities, totals and critical workflows before the team switches systems.
Explore the proposed workflow
Worked exampleRevenue & CRM
Three revenue numbers, three different questions
Explain why the CRM, invoice ledger and bank don't agree. Preserve the different dates and definitions instead of forcing one revenue total.
Explore the proposed workflow
Worked exampleFinance & delivery
Don't start onboarding with half a handoff
Check scope, stakeholders and dependencies before creating the onboarding project. Missing information needs an owner, not another welcome email.
Explore the proposed workflow
Worked exampleReliability & support
An escalation needs an owner, not a louder notification
Keep urgent tickets visible through acknowledgment and resolution. Separate priority, response clocks and incident ownership so alerts have a next action.
Explore the proposed workflow
Worked exampleFinance & delivery
Match a Stripe payout without losing the fees and refunds
Trace a bank deposit to the Stripe transactions it settles. Keep fees, refunds and unsettled activity out of a misleading sales total.
Explore the proposed workflow
Worked exampleApprovals & review
An approval belongs to the request that was reviewed
Tie approval to a request version so changed amounts, suppliers or terms can't slip through on an old decision.
Explore the proposed workflow
Worked exampleApprovals & review
Extract the invoice fields. Keep the payment decision.
Turn incoming invoices into proposed records with field-level checks. A readable PDF and a confident model are not enough to authorize payment.
Explore the proposed workflow
Worked exampleReliability & support
Replay a failed event without repeating the business action
A retry must know which actions already happened. Separate event receipt, processing and business effects so recovery doesn't create duplicates.
Explore the proposed workflow
Worked exampleReliability & support
Let AI propose the queue. Let support own the decision.
Classify support requests into a bounded set of queues, show the evidence and review uncertain cases. Keep customer replies and account actions outside the classifier.
Explore the proposed workflow
Put the thinking to work
Bring the handoff that
keeps breaking.
A redacted record, a process sketch or one awkward exception is a useful starting point. We’ll help define what should happen next.