Friday 22 May

Engagement · First six months

What the first six months looks like.

Not a roadmap. Three four-week phases then a longer narrative. Built around getting the systems Growth Fulfilment already has to talk to each other first, then around how the team actually works, then learning. The portal stays yours at month 6.

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

  • Phase

    Weeks 1–4

    Data and APIs — connecting the systems Growth Fulfilment already has.

    The data exists; it just isn't talking to itself. Pipedrive, the WMS, accounting, Trustpilot, the carriers and the Service Health feeds for Marker Beverages and the other brand customers all read into the portal during the first month. Pulling, cleaning, mapping, sanity-checking. Replacing illustrative numbers with Growth Fulfilment's actuals across every surface you saw at the pitch.

    What gets worked on

    • ·Pipedrive read-access provisioned — the Commercial Engine runs against the real pipeline.
    • ·WMS data-pipe with Adrian — what reads cleanly, what needs a connector. Operations Cockpit reflects the actual SLA and exception data.
    • ·Accounting feed with Darragh — annualised run-rate, GP% per client, top-10 by revenue, real on the Projections page.
    • ·Marker Beverages Service Health: Shopify, Trustpilot and the carrier mix wired into the Stickiness Layer.
    • ·Top-10 client list confirmed, sensitivity flags set before any of those clients land in the cockpit.

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

  • Phase

    Weeks 5–8

    Built around the team — surfaces reshape around how Growth Fulfilment 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 Charlie and William — Brand Studio queue moves from illustrative drafts to drafts in your own register.
    • ·Charlie's daily action view runs against the real pipeline with the people he actually works with.
    • ·Pre-meeting briefs and the note-taker pipeline run against live diary signal.
    • ·First standing cadence call runs the full agenda; the action ledger goes live.
    • ·Adrian's exception flow on Operations Cockpit shaped around how his team already triages.

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

  • 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.
    • ·ICP scoring tuned against the deals that have closed in months 1–2.
    • ·Stickiness Layer outputs reviewed with William; 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.

  • 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 where another set of eyes shifts the close. System refinement against the patterns of the first three months and beyond. Brand Studio voices and Stickiness Layer outputs settle into their cadence. Handover prep builds toward month 6 — documentation, infrastructure handover plan, optional partnership terms agreed before the rights transfer.

What Growth Fulfilment brings

  • ·Pipedrive read-access during the first month — read-only token, sandbox first.
  • ·WMS read-access during the first month — Adrian and Growth Fulfilment's tech contact in the same room.
  • ·Accounting feed during the first month — Darragh in finance.
  • ·M365 calendar read for Charlie and William, delegated where it makes sense.
  • ·A handful of LinkedIn posts you've each been pleased with — the anchor for voice calibration in month two.
  • ·Top-10 client list confirmed and sensitivity flags before those clients land in the cockpit.

What Trent brings

  • ·The portal — built around Growth Fulfilment's actual data and workflows. Yours to keep, outright, at month 6.
  • ·Commercial pipeline support alongside the build — deal reviews, meeting structures, sales coaching — for the full six months.
  • ·Brand Studio drafts in Charlie and William's calibrated voices, once voices are calibrated.
  • ·A standing cadence call once the rhythm settles.
  • ·£6,500/month, 30-day notice either party. Portal handed over at month 6, outright rights transfer.
  • ·Optional £500/month from month 7 for upkeep, infrastructure and light iteration. Opt-in, not bundled.

At month 6 · handover

  • ·The portal — full rights — transferred to Growth Fulfilment, outright.
  • ·Documentation: what each surface is, how it runs, who owns what.
  • ·Infrastructure handover plan agreed. Hosting, integrations, credentials.
  • ·Decision on the optional £500/month ongoing partnership sits with Growth Fulfilment.

Weeks 1–4 are the data month. Weeks 5–8 reshape the surfaces around how the team works. Weeks 9–12 are learning and handover prep. Months 4–6 carry the commercial work alongside the build. £6,500/month for six months, 30-day notice either way. The portal, outright, is yours at month 6. Optional £500/month from month 7 covers upkeep, infrastructure and light iteration. Opt-in.