New products, designed and engineered to survive contact with real users.

The problem

Teams commit budget to a feature list before anyone has tested whether the underlying problem is real or whether the proposed solution addresses it.

What the work involves

We run structured discovery: stakeholder and user interviews, a review of the systems and data you already have, competitor and comparator analysis, and options modelling. We convert findings into a prioritised capability map split across MVP, Release 1 and Later, each with assumptions and evidence attached. Where evidence is thin we say so and propose the cheapest way to get it.

Typical deliverables

• Discovery report with sourced findings
• Prioritised capability map (MVP / Release 1 / Later)
• Assumption and risk register
• Costed delivery options with trade-offs

The problem

Digital products frequently fail at the seams — the offline step, the call centre, the letter, the third-party handoff — which never appear in a wireframe.

What the work involves

We map the end-to-end service including the parts that are not software: the back-office process, the phone call, the paper form, the partner integration. We run interviews and usability testing with representative users, including users with access needs and low-bandwidth conditions where relevant to your audience.

Typical deliverables

• Service blueprint covering front-stage and back-stage
• User research findings with recordings and quotations
• Journey maps with pain points and opportunities
• Accessibility and inclusion findings

The problem

Design handovers that cover only the ideal path force engineers to invent the loading, empty, error and permission-denied behaviour — inconsistently.

What the work involves

We design the full state matrix for every significant component, define the responsive behaviour from 320px upwards, and specify keyboard, focus and screen-reader behaviour. The output is a design system with tokens and documented components rather than a set of static frames.

Typical deliverables

• Design system: tokens, components, usage rules
• Full state coverage: loading, empty, populated, error, permission-denied
• Responsive specifications across five breakpoints
• Accessibility annotations to WCAG 2.2 AA

The problem

Brand-led websites are often beautiful and unusable: slow, inaccessible, impossible for the marketing team to edit, and disconnected from the sales process.

What the work involves

We build content-managed sites on modern rendering architectures with performance budgets enforced in CI. Content editors get structured editing with draft, review and publish states. Conversion paths connect to your CRM so enquiries are routed and measured rather than emailed into a shared inbox.

Typical deliverables

• Content-managed site with editorial workflow
• Performance budgets enforced in the build pipeline
• Structured data, metadata and redirect management
• CRM-connected conversion paths with analytics

The problem

The difficulty in a platform is rarely the feature list. It is tenancy, permissions, billing edge cases, and making sure one customer can never see another customer’s data through any route.

What the work involves

We design the tenancy and permission model first and enforce it in the database as well as the interface, so a bug in the application layer cannot become a data breach. We test isolation positively and negatively for every role, across the API, search, exports, realtime channels, file storage and error messages.

Typical deliverables

• Tenancy and permission model with a written role matrix
• Database-level access policies with automated positive and negative tests
• Billing, subscription and entitlement handling
• Admin, moderation and support tooling

The problem

Mobile projects underestimate the operational surface: store review, privacy disclosures, device fragmentation, offline behaviour and release management.

What the work involves

We choose native or cross-platform based on your actual requirements — hardware access, performance profile, team composition, release cadence — and say why. We build for intermittent connectivity where your users need it, and we handle the store submission process including data-safety disclosures and account-deletion requirements.

Typical deliverables

• iOS and Android applications with automated build and release pipelines
• Offline and low-bandwidth behaviour where the audience requires it
• Store listings, privacy disclosures and data-safety declarations
• Crash reporting, analytics and staged rollout configuration