CUSTOMER SYSTEMS

When the process needs more than a website.

A booking, ticketing, membership or customer workflow should be built around a real need, not a list of possible features. We investigate that need, agree a useful release and build only what belongs in it.

Is this the right level of work?

This may be appropriate when a recurring process involves unnecessary manual handling, information gets lost between tools, or an important requirement is not adequately served by your current setup. There needs to be a responsible owner, an operating plan and a benefit that justifies the build and ongoing care.

If a standard service already does the job well, we may recommend that instead.

FIRST, FEASIBILITY · FROM £3,000

Resolve the uncertainty before the build.

  1. 01

    The process and people

    Map the process, identify users and access needs, and examine the relevant data and integrations.

  2. 02

    The right approach

    Compare existing products with a custom approach and test the main uncertainties. A limited prototype or technical test is included where it resolves the agreed risk.

  3. 03

    A defined first release

    Receive a recommendation, operating responsibilities and acceptance criteria. You can decide not to proceed.

THEN, AN AGREED BUILD

One useful release. Clearly bounded.

One reference release is an event journey: choose an event, pay, receive a ticket and check in, with the agreed staff administration behind it.

01

The £16,500 reference build

One business and existing identity, up to five public pages, two user roles, up to three named workflows, two integrations using supported documented APIs and one import of up to 500 clean records.

02

Named, testable work

The actual screens, actions, reporting and acceptance tests must be named. These counts do not mean that any three workflows cost the same.

03

Implementation and handover

Responsive implementation, agreed administration, testing, documentation, two training sessions and 45 days of original-scope defect correction.

04

Not silently included

Memberships, marketplaces, complex commissions, custom AI and product configurators are not automatically included. If the required release is different, the quote is different.

Control and handover.

We agree who controls the accounts, data and assets, which suppliers are involved and how the system is maintained. You should understand how to operate the result and how another appropriate supplier could take over. A custom build still has hosting, software and maintenance dependencies.

Discuss the process you need to improve →

RELATED WORK

See the thinking in practice.

Connected journeys for events, programmes and personal-brand content. These records show individually scoped work, not an identical fixed-fee release or a promise of future business results.

Exec Branch Legacy Conference panel on stage
Community platform

Exec Branch

Ruth Kudzai seated in a burgundy cape suit
Personal brand & operating system

Ruth Kudzai

After launch

Included defect correction covers the agreed original work for its stated period. Optional ongoing care is a separate arrangement with named responsibilities and limits. It is not unlimited development or a guarantee of round-the-clock support.

Reference care: £300 per month for up to two hours on the defined standard site, or £600 for up to four hours on the defined platform. Hosting and tools are separate. Available only where capacity has been agreed and the relevant system is listed.

Small agreed changes can use a £750 block of up to five hours. Larger or uncertain work receives its own proposal. The estimate, schedule and treatment of unused funds are agreed before you pay.