Delivery staffs a scope it never saw.
Outsourcing and shared services run two businesses at once — a bid desk selling seats, transactions and outcomes, and a delivery org that has to staff them. We build the system that holds both, from RFP to ramp to the quarterly review.
The promise lives in the bid, not the system.
Scope, service levels, rate card and shift coverage are written into an RFP response and an SOW, then never land anywhere structured. Operations rebuilds them in a spreadsheet, finance invoices from a third version, and nobody can say what was actually sold.
Sold by the seat, staffed by hand.
BPO — rampThe spine of a bid-to-ramp operation.
The bid pipeline
Deal stages that match a real pursuit — RFI, site visit, solution design, pricing committee, best and final, MSA and SOW — with the security questionnaire and the bid team held on the deal.
Pricing on the record
Seat-based, per-transaction and outcome-based line items quoted as products, so a deal carries FTE count, shift coverage and rate card instead of an attached workbook nobody versions.
Ramp tied to closed-won
A signed deal generates the hiring plan: seats by wave, class start dates, training and nesting, go-live. Recruiting works from the deal record, not a message in a channel.
Sales to delivery handover
A transition record built from the deal — scope, service levels, escalation path, named client contacts — with an operations lead accountable to it before kickoff, not after.
SLA and QBR reporting
Service levels, quality scores and seat attrition pulled from the workforce and ticketing systems into the client review, so the QBR deck is generated rather than assembled.
Multi-country, multi-entity delivery
Delivery centers, contracting entities and currencies modelled properly, so every deal knows which site delivers it, which entity bills it and whose headcount it consumes.
Bid desk to delivery floor, in order.
Diagnose
One recent pursuit walked from the bid desk through workforce management to the delivery floor: how it became a signed SOW, and where scope stopped being written down.
Define
One contract model — pricing units, SLA definitions, ramp stages, site and entity ownership — agreed by sales, operations and finance in the same room.
Build
HubSpot rebuilt against that model: bid pipeline, quoting, the transition record, integrations to WFM, ticketing and HRIS, and client-facing reporting.
Hand over
Runbooks for the bid desk and the transition team, training on both sides of the handover, and a quarter running it beside your operations leads, through one full ramp.
Change orders are where the model drifts.
Scope moves after go-live — another queue, another language, an extra shift, a holiday coverage clause. When change orders never reach the deal record, what finance invoices and what operations staffed stop agreeing, and the account looks profitable until the year-end true-up.
Protege
AI and data exchange — United StatesSales through delivery orchestrated across HubSpot, Make, ClickUp, Slack and Linear, with HubSpot as the single source of truth.
Proof 02Regency Health Care
Home care — New York CityHIPAA-compliant process transformation from intake through aide management, modelled in BPMN before a pipeline was built.
Proof 03Jamming
Events — LimaB2B and B2C operations cleanly separated, overlapping tools removed, and a lean stack built around HubSpot.