Sales Desk
We needed a CRM that carried the customer from first conversation into fulfillment. So we built one.
RUNNING INTERNALLYA real Lehvel operating system in use internally. Not a customer product claim.
01 Conversation or audit02 Relationship created03 Business Truth captured04 Readiness reached05 Fulfillment request sent06 Execution state visible
01 · Question
What happens when a sales system is designed around the sale and the fulfillment handoff instead of around the CRM?
02 · Why it matters
A rep sits with a contractor or a restaurant owner, learns the business, and then retypes it into a second tool for the people who build the work. That retyping is where facts die. We sell websites built from Business Truth; the sales record had to be that truth.
03 · State
RUNNING INTERNALLY A real Lehvel operating system in use internally. Not a customer product claim.
04 · What we built or tested
- One Lehvel-operated platform for direct reps and reseller partners, with role-based access.
- A shared prospect pool with atomic claim/ownership: everyone sees the pool, one rep claims, only the owner works it, admin can reassign.
- Chronological notes and activity; Business Truth intake; deterministic readiness and completeness.
- One relationship lifecycle instead of separate Lead and Client apps; a structured, idempotent fulfillment request into delivery.
- Mobile-first Today / Prospects / Active workflows, with a real PostgreSQL migration set and a reproducible database test path.
05 · Evidence
Data layerNine migrations plus sync, provisioning and test tooling
Lifecycleconversation → relationship → Business Truth → readiness → fulfillment request → execution state
QABrowser-level, rendered mobile QA found defects unit tests and builds did not
06 · What we learned
- The interesting part is continuity: the same structured record moves through sales and fulfillment instead of being retyped.
- Green unit tests and a green build were not a passing product. A phone in a hand was.
07 · Limitations
- Running internally for our own sales operation. Not a customer product and not offered as one.
- Adoption and volume numbers are not published; they would be traction theater.
08 · What changes next
Harden the fulfillment handoff so a build request carries every fact delivery needs on the first pass.
Negative results are published as results. A state on this page is a claim about what is true today, not about what is planned; a limitation is a limitation.
Tell us what is true about your business.
A few questions, in your own words — type them or talk. A person reads what you send and follows up. Nothing is published and nothing is sent on your behalf.