A few useful things to know.

We work with established organisations and operational teams dealing with consequential, interconnected work: service businesses, public-interest organisations, regulated services, logistics, property operations, and membership organisations. The common thread is a real service challenge that needs both thoughtful design and practical engineering.

We shape engagements around the decision or delivery need, rather than a fixed package. Some begin with a focused discovery or service mapping phase; others need a multidisciplinary team through design, software delivery, and adoption. We will be candid if the scope is too small or too broad for a useful start.

No. A clear description of what is difficult, who it affects, and any constraints is enough. Discovery is specifically designed to turn competing views and incomplete evidence into a shared, testable direction.

We talk with stakeholders and people doing the work, review existing evidence and systems, map important workflows, and test assumptions where possible. We bring the findings back as an agreed problem frame and prioritised next steps, not a report that sits on a shelf.

The work we create for a client is transferred under the terms agreed for that engagement. We clarify ownership, licensing, third-party dependencies, documentation, and access before delivery begins so there are no surprises at handover.

Yes, where access, security, and technical conditions allow. We identify integration boundaries early, establish which system is authoritative for each kind of data, and prefer resilient, understandable connections over hidden coupling.

Accessibility is part of product quality and is considered from research and interaction design through implementation and testing. We use accessible patterns, keyboard and assistive-technology checks, clear content, and the relevant standards for the project and intended audience.

We work in visible, reviewable increments. Regular demonstrations, written decisions, shared priorities, and direct collaboration keep stakeholders involved while the team builds and validates. We adapt the cadence to the organisation instead of insisting on a ritual for its own sake.

We can plan a support and improvement period as part of an engagement. Existing clients can use the Support page to report an access issue, software defect, data question, change request, or project follow-up.

Timing depends on the service, systems, dependencies, and decisions involved. A bounded discovery may take a few weeks; a substantial product or modernisation effort may take several months or longer. We estimate after understanding the constraints and explain what could change the plan.

Yes. We work with international teams and plan for time zones, local service rules, language needs, and different operating contexts. Our delivery routines make decisions and progress visible for people who are not in the same room.

No. We collaborate with internal product, operations, design, and engineering colleagues, bringing the capabilities or capacity the work needs. We aim to leave the team with clearer systems and stronger ways of working.