00 / Arrival
An independent strategy, design and technology practice.
Compelete designs what businesses need next — and makes it work. One senior team from the business problem through to the system that runs afterwards.
01 / The problem with problems
Business problems rarely arrive in neat categories.
They arrive as a symptom. A channel that does not convert. A brand that no longer matches the operation. Three systems that will not speak to each other. A team doing by hand what should have been designed once.
The category is usually the last thing that becomes clear, which is why we do not start with the deliverable.
02 / Possibility
You arrive with a candidate answer. Strike out the ones that are really symptoms.
You may think you need
We'll work that out first.
03 / Invitation
Bring us the business problem.
Not a shopping list of deliverables. The first thing we design is the definition of what is actually wrong.
04 / Composition
Not everything needs to be built.
Everything needs to be designed.
Most of what a business needs already exists. The work is choosing the right materials, then designing how they behave together.
Materials
Select materials to compose a system. Space or Enter toggles each one.
- WHATSAPPCOMPOSE
- OPERATIONSDESIGN
- CRMCOMPOSE
- PAYMENTSCOMPOSE
One working system.
3 composed from what exists1 designed0 built
- Where the customer already is
- OPERATIONS
- Who does what, when it escalates
- CRM
- One customer record, not four
- PAYMENTS
- Licensed, certified, already solved
05 / A worked example
The answer might be WhatsApp.
A customer who already messages a business does not want an app to download. The commercial question is not which channel to add — it is what has to be true behind the channel for the conversation to complete.
- 01 · EXISTSCustomerEnquiryBookingReorderSupport
- 02 · EXISTSWhatsApp BusinessBusiness platformTemplatesCatalogueVerified identity
- 03 · DESIGNED BY USDesigned orchestrationConversation designRouting rulesHuman escalationConsent & retentionMeasurement
- 04 · EXISTSSystems of recordCRMCommerce & cataloguePaymentsAnalytics
One conversation the business can actually operate.
Four of these five layers already exist and are composed. The layer that decides whether it works is the one that has to be designed.
06 / Evidence
Signal Case 001
The first published Compelete Signal assessment. The reasoning chain — evidence, observation, interpretation, the competing explanation, the decision — is published in full at /signal.
Agents for Data agreed to be assessed under Compelete Signal and to be named as its first published case.
Publish named, under written owner permission recorded 27.08.26, with claims limited to the admitted set. Permission to be named does not widen what may be claimed.
The Signal assessment protocol and its publication gate: five gates, an admitted-claims register, and a permanent anonymised variant that renders whenever permission or a gate fails.
Not published as a business metric. The admitted claims and their qualifiers are stated at /signal and are not restated, compressed or extended here.
07 / Capabilities
Six connected capabilities. Not six departments.
Most engagements use three or four. They are listed as verbs because they describe what gets done, not who owns a budget line. See how they connect →
THINK
StrategyResearchPropositionCustomer journeysBusiness architectureMeasurement
DESIGN
IdentityExperienceInteractionContentDesign systemsInterfaces
BUILD
WebApplicationsPlatformsCommerceCloudIntelligent systems
CONNECT
APIsCRMWhatsApp BusinessPaymentsAnalyticsAutomationPartner technology
RUN
MonitoringExperimentationOptimisationSupportContinuous development
COMMISSION
Connected objectsPhysical/digital interfacesInstallationsInstrumentsExperimental interfaces
08 / Start
We design what businesses need next. Then make it work.
Tell us what isn't working. We'll work out what it needs.
Start with a problem