What the first six months looks like.

Phase shape · weeks 1–12, then months 4–6

1. Phase

   Weeks 1–4

   Data and APIs — connecting the systems InterSend already has.

   The data exists; it just isn't talking to itself. Mintsoft, the existing CRM (or the spreadsheet that's become one), accounting, comms, carriers, customer commerce stacks, reputation feeds and brand-customer Service Health signals all read into the portal during the first month. Pulling, cleaning, mapping, sanity-checking. Replacing illustrative numbers with InterSend's actuals across every surface you saw at the pitch.

   What gets worked on

   • ·Mintsoft (WMS) read-access — Operations cockpit and Service Health both read live.
   • ·Accounting feed — Xero / Sage / QuickBooks, whichever is in use. Run-rate baseline + per-brand-customer profitability land on Financial Pulse and Projections.
   • ·CRM read — existing pipeline data into the Pipeline page (HubSpot / Pipedrive / Salesforce / spreadsheet).
   • ·Microsoft 365 calendar and inbox read — delegated where it makes sense across the commercial team.
   • ·Carrier APIs — Royal Mail, Yodel, DPD, FedEx, Evri — fulfilment performance into Service Health and Live Ops.
   • ·Per-brand-customer Shopify (with consent), Trustpilot and Google Reviews — Service Health goes live for the pilot brand customer.
   • ·LinkedIn Sales Navigator — pipeline signal + Content Engine engagement attribution.
   • ·WhatsApp Business + email notification wiring — for brand-customer service alerts.

   By endBy the end of week 4 the surfaces you saw at the pitch carry InterSend's actual numbers.

2. Phase

   Weeks 5–8

   Built around the team — surfaces reshape around how InterSend works.

   Data is real. The workflows wired in. Approval queues populated with real drafts in calibrated voices. First standing cadence runs. The portal stops being demo-shaped and starts being team-shaped.

   What gets worked on

   • ·Voice calibration with John, Jamie and Laurence — Content Engine queue moves from illustrative drafts to drafts in your own register.
   • ·John's morning view runs against the real pipeline with the accounts each rep actually works.
   • ·Pilot brand-customer portal signed off by the brand directly — usable inside their own login.
   • ·First standing cadence call runs the full agenda; the action ledger goes live.
   • ·Operations baseline with your ops lead — exception flow on the cockpit shaped around how their team already triages.

   By endBy the end of week 8 the team is using the portal in the rhythm of their existing week.

3. Phase

   Weeks 9–12

   Learning and handover prep — the system starts adjusting to behaviour.

   Approval patterns settle. Draft voices tighten. The portal stops needing constant calibration and starts adjusting to behaviour — what gets approved, what gets edited, what gets ignored. Handover documentation drafted toward the month-6 rights transfer.

   What gets worked on

   • ·Voice drafts refining against the edit pattern of the first two months.
   • ·Cadence call format settling — what's a useful thirty minutes, what isn't.
   • ·Pipeline stage transitions tuned against the deals that have moved in months 1–2.
   • ·Service Health outputs reviewed with John; carrier-mix or pricing decisions surfaced for action.
   • ·Handover documentation drafted — what the portal is, how it runs, what the optional ongoing partnership covers.

   By endBy the end of week 12 the portal is running quieter — surfaces lifting the work, not generating new work.

4. Phase

   Months 4–6

   Partnership in flight — commercial work alongside the build.

   Trent in alongside the build. Pipeline coaching, meeting structures, sales process and business development — the human layer the portal can't replicate. Deal reviews. Sales support on live calls. System refinement against the patterns of the first three months. Content Engine voices and Service Health outputs settle into their cadence. Handover prep builds toward month 6 — documentation, infrastructure handover plan, optional partnership terms agreed before the rights transfer.