Drones, connected vehicles, fleet trackers and fixed sensors, managed across NB‑IoT, LTE‑M, LTE and 5G. Every enterprise deal reaches that fleet through one pipeline: lead conversion, a nine-section technical intake, quote, custom pricing, contracting.
It ran on disconnected internal tooling and manual intervention. This is the end-to-end redesign onto a single architecture.
Shown as mockup representations — the shipped production screens are under NDA.
*yes, i meant to put the em dash above
The queue does the triage. Pardot behavioral grade and Einstein propensity score are pre-computed; the seller inherits a ranked list, not a cold pile.
Connected-vehicle fleet — embedded eSIM, EU + US roaming. Flagged by the “connected vehicles?” gate for the IoT Connectivity framework.
Landing-page views in the top 5% of all prospects this quarter.
No form-tracker click-through in the last quarter.
Book solution-architect intro — fleet size clears the framework threshold.
The record answers “why this one, why now.” Consent status, Einstein score, and a single recommended action sit beside the facts so the AE opens with context, not discovery.
Book technical discovery with the ISA before the intake.
The opportunity is the hub. It names every owner and holds the related quotes, orders and intakes; sellers launch the nine-section IoT intake directly from here, and drive the deal toward quote-to-contract.
One answer sets the technology tier; the rest is derived from it.
A near-hour form became a guided path. One technology choice derives APN, eSIM, throughput and dormancy — the AE confirms rather than re-enters, and downstream pricing reads the same fields.
| Tier | SIM range | On-net data | Overage | MRC |
|---|---|---|---|---|
| Tier 1 | 1 – 5,000 | 8 GB | $0.011/MB | $4.60 |
| Tier 2 | 5,001 – 15,000 | 8 GB | $0.009/MB | $4.10 |
| Tier 3 | 15,001 – 30,000 | 12 GB | $0.007/MB | $3.80 |
| Tier 4 | 30,001 – 38,500 | 12 GB | $0.006/MB | $3.55 |
Custom and special pricing, sized once. The tier table is computed from the fleet size captured at intake; the approval routes to sales leadership with the delta from rack rate already shown.
This Master Corporate Service Agreement (the “Agreement”) governs the provision of connected-device wireless services set out in Schedule A — IoT Connectivity, incorporating the approved rate framework and the terms below. Capitalized terms have the meanings given in Section 1.
Hi Marcus,
Your IoT Connectivity agreement is ready. It reflects the approved tiered pricing and the 38,500-line commitment from quote QtO-20241015. Please review and apply your signature — the Provider has already counter-signed.
The contract is a quote that signs. Schedule A generates straight from the quote — same lines, same approved tiers — then routes for e-signature; the Provider counter-signs first, and the audit trail travels with the record.
Downstream: the generated quote. Derived configuration flows into CPQ pricing without re-keying; credit ceilings and line availability sit beside the totals so checkout isn’t blocked by a surprise.
IoT connectivity is the cellular service that links a fleet of devices back to the business running them.
Fig 1 · The connectivity spectrum the intake configures against. Four network technologies, from large low-power fleets to mission-critical workloads. The intake's network section maps each deal onto this curve.
T‑Mobile for Business was moving prospecting and QTC / CPQ onto a new version of Salesforce on a new backend.
Everything else on the platform sold from a catalog line. IoT connectivity has none.
The nine-section intake was the visible pain.
So the scope was the whole flow: an Einstein-ranked lead through opportunity, intake, quote, pricing and contracting. What follows is what shipped inside the real constraints of two PM organizations, an enablement team and a CRM-generic design system. Where it matters, I show the version I would ship without them.
Fig 1 — The deal-flow the framework now lives inside, on the consolidated platform. Intake feeds quote logic and custom pricing directly, not just the next step. The dashed edge is the reopen path: renegotiation at contracting edits pricing state, not documents.
Two candidate accounts returned for “Atlas Logistics, Seattle”
Prospecting comes first. Pardot grades each account on engagement (a good / better / best stoplight) and Einstein scores predicted conversion next to it. My design problem was trust: sellers ignore a black-box score. The queue exposes why a lead ranks (grade, score, recency) so the ranking earns the right to order someone's morning.
Creation, prospecting, disqualification, conversion — four states, one surface. The first question the system asks is whether this customer already exists: candidate accounts and contacts come back scored for confidence and flagged for what is already in CRM, so the seller confirms a match, disqualifies, or creates a record deliberately. It is the cheapest place in the pipeline to prevent a duplicate customer, and the most expensive one to skip.
Work top lead opens Convert: find or create the contact, attach the account, and the new opportunity inherits everything — Einstein score, consent state, duplicate warnings. Nothing is re-keyed between prospecting and sales.
Everything hangs off the opportunity: the AE assembles the team, then launches work from it — start the IoT intake, create a quote (there can be many), kick off quote-to-order. One record owns the deal; every artifact that follows keeps a pointer back to it.
The intake replaced a Salesforce dual-list-picker maze with nine explicit sections. Each section is independently saveable and recoverable; a seller can stop mid-deal and another can resume with full context.
Everything in the intake routes one of two ways: catalog items flow straight to quote logic; non-catalog needs become structured exceptions instead of email threads. Making the fork explicit is what lets the clean path stay fast.
Connected-vehicle and SASE bundles, volume discounts, multi-year terms: the pricing surface composes them as visible deal components, each with its own approval chain. The seller sees what's standard, what's exceptional, and who owns the exception.
Legal sits with contracting; its job is reviewing the pricing team's work. A linear flow under-describes the real problem: dependencies, exception routes, ownership boundaries. The fix wasn't moving legal earlier; it was handing legal structured pricing output (typed components with approval chains) instead of email threads, so review starts from state, not archaeology.
Every clause traces back to the intake section and pricing component that produced it. The package is traceable, reviewable, and handoff-safe; when negotiation reopens, the team edits state, not documents.
The signed quote drops straight into provisioning as typed order lines: SIM and eSIM activations, gateways, connectivity plans. Each line keeps its lineage back to the priced component, so fulfillment never re-keys the deal, and every line carries its own status from queued to provisioned.
The fulfilled order instantiates the account hub: orders, SIM activation, fleet status, billing. Post-sale telemetry feeds the next renewal's lead score; the journey is a loop, and the design closes it.
Written with engineering before pixels. If a screen can't satisfy these, the screen is wrong, not the criteria.
AC-01Every intake state is resumable by a different seller with zero verbal handoff.AC-02Every exception has an owner and a visible status the customer-facing seller can read.AC-03Every price component shows its approval chain before submission, not after rejection.AC-04Every contract clause traces to the intake section and pricing component that produced it.AC-05Reopening a deal edits state, not documents: no re-keying on renegotiation.Outcomes were read jointly with business stakeholders and the business product managers who own the pipeline numbers — directional, not audited. Alongside the metrics: the shorter flows in this system were delegated to senior designers I trained on the framework, which is its own outcome.
From most-of-an-hour to minutes end to end · same AE cohort.
Roughly half as many sections returned by Solution Architecture.
Median time-in-stage across the first 90 days of deals.
Against sustained complaints on the legacy form it replaced.
The framework is a baton crossing five organizational boundaries. Once that was named explicitly, every interaction decision (chip vs dropdown, conditional show/hide, smart defaults) had a principled answer.
Both are sitting in review. The version on this page is what shipped under enterprise design-system constraints; the unconstrained version would have launched months earlier.
I owned the intake architecture, the exception model, and every cross-boundary handoff. The shorter flows — demo requests, order enrichment, status surfaces — went to senior designers I trained on the framework, with acceptance criteria as the contract. Review was against the ACs, not my taste.
Einstein orders the front of the pipeline today. The proposed next step is an LLM pass that drafts intake sections from the lead's own artifacts — RFQs, meeting notes — with the AE confirming instead of typing. Same principle as the queue: the model proposes, the human owns.