Engagements

How engagements run

The Desktop Maple sequence from scoping call to acceptance — built for e-commerce platform integration and customisation work.

Programming consulting for e-commerce platforms only works when everyone shares the same picture of an order’s life. This page is that picture for Desktop Maple clients.

The sequence

1

Scoping call

We confirm platforms, partners, peak dates, and whether a Platform Integration Engagement, Customisation Review, or Go-live window is the honest fit.

2

Discovery artefacts

Order-state diagrams, interface inventory, and a risk register focused on checkout, stock, and refunds — not a slide deck of aspirations.

3

Build oversight

Paired sessions with your developers or agency against the written map. Scope changes are logged; they do not silently expand.

4

Acceptance & cutover

UAT checklist, rehearsal, and optional standby. Trading continues with a known rollback path.

What you bring

  • Admin access or guided walkthroughs
  • Sample orders that show refunds, splits, and pre-orders if you sell them
  • Named approver for production changes
  • Honest calendar for peak trading freezes

What we refuse to pretend

We will not promise “seamless” anything. We will say which interfaces are brittle, which tests must pass before cutover, and which items belong in a later phase.

Start the conversation

Ready to walk through your stack? Request a scoping call or read the flagship engagement brief.