Labs / Systems · Updated 2026-09-11
Sales Desk
Our client sites run on checked facts, so our sales record does too. One system carries a customer from first conversation into delivery.
In useRunning in our own work and in client work. Delivered through Lehvel engagements, not as self-serve software.
- Conversation or audit
- Relationship created
- Business Truth captured
- Ready to hand off
- Request sent to delivery
- Progress visible
What we asked and what we found
Every entry answers the same eight questions, in this order.
Question
What happens when a sales system is built around the sale and the handoff to delivery, not around the CRM?
Why it matters
A rep learns a business, then retypes it into a second tool for the people who build the work. That retyping is where facts die.
State
In use Running in our own work and in client work. Delivered through Lehvel engagements, not as self-serve software.
What we built or tested
- One Lehvel-run platform for direct reps and reseller partners, with access by role.
- A shared pool of prospects: one rep claims a prospect, only that rep works it, and an admin can reassign it.
- A running log of notes and activity, a Business Truth intake and an automatic check of how complete each record is.
- One lifecycle for each relationship, not separate lead and client apps, and one clear request that hands the work to delivery.
- Phone-first Today, Prospects and Active views.
Evidence
- One path
- Conversation, relationship, Business Truth, readiness, request to delivery, progress
- Testing
- Checks on a real phone found defects that unit tests and builds did not
What we learned
- The point is continuity: the same structured record moves from sales to delivery without being retyped.
- Green tests and a green build were not a passing product. A phone in a hand was.
Limitations
- It runs Lehvel's own sales. It supports the work we sell and is not a separate product.
- We do not publish adoption or volume numbers. They would be for show.
What changes next
Make the handoff to delivery carry every fact the builders need the first time.
Failed tests are published as results. A state on this page describes today, not plans.
Next in Labs
- Next: How Lehvel's AI systems hand work to each other
We got tired of carrying prompts and status between AI systems by hand. So we built a shared system that does it, with GitHub as the record.
Systems
Get Upstream
One email a week: what we asked the AI, what it got wrong, and how we checked.
Our research reaches 17,000+ followers across our channels. Upstream is the weekly version.
Weekly. Unsubscribe anytime. Privacy
