Product Design & Interface Systems
Map the work, test the screens, and document what developers need.
- User tasks and constraints
- Information structure and journeys
- Wireframes and prototypes
Understand your business. Design, build and care for your system — from the first brief to daily use.
Consult · Software · Infrastructure · Care
From customer-facing screens to the data and infrastructure behind them. Commission a specific part or plan how the pieces work together.
Start with the people using the product, then design around its data, workload, and the team maintaining it. From content-driven websites to internal business applications.
Make the small screen work harder. Use React Native for shared application code or Swift for direct access to platform capabilities, with clear tradeoffs from the start.
Build infrastructure around the actual workload. Separate environments, make changes traceable, and prepare recovery procedures before they are needed.
Map the work, test the screens, and document what developers need.
Clear data boundaries, access rules, and system integrations.
Understand the existing system. Prioritize fixes. Make changes traceable.
Start with the tasks, the data, and the systems already in place. Then decide what belongs on the web, a phone, or a desktop. These are examples of the work we take on, not a limit on the scope we consider.
Systems and technologiesCompany sites and published content can use static or prebuilt pages. Member areas, bookings, and commerce need a backend to manage data, permissions, and transactions. We choose rendering and caching per route, and design publishing tools around the people who maintain the content.
Some work needs access to local files, connected devices, or processes outside a browser. We build installed applications, command-line tools, and background services. Operating-system APIs, permissions, and distribution requirements guide the choice between native and cross-platform implementations.
iOS and Android applications need to account for screen sizes, cameras, notifications, and unreliable connections. We define offline behavior, data synchronization, and access rules before testing on the agreed devices and preparing the release process.
Connect websites, applications, accounting, inventory, and external services with explicit data formats and access rules. Plan for unavailable endpoints and repeated requests. Automated changes to important records need an audit trail, duplicate checks, and a way to pause or request human review.
A full rebuild is not the starting assumption. Choose a scope around the problem that needs attention and the information available today.
For a business with a workflow but no suitable tool, or a product being developed for the first time. Establish what the first release needs to prove before expanding it.
For software that still serves its users but has manual steps or missing functionality. Understand its constraints and test how changes affect existing behavior.
For a system that is slow, unreliable, or difficult to maintain. Reproduce the problems, collect evidence, and order the improvements before agreeing the work.
Each stage produces work you can review and decisions we need to make together. We distinguish defects from added scope and assess the effect on cost and schedule before changing the plan.
Read the process and preparation checklistUnderstand current workflows, users, and constraints. Prioritize what the first release needs and record what remains outside the scope.
Output: Brief, scope, and acceptance criteria
Map user journeys, screens, data, and system boundaries. Check important assumptions before committing to details that are expensive to change.
Output: Screen prototypes and system design
Develop in reviewable increments, with code review and testing alongside implementation. Make progress and outstanding decisions visible.
Output: Working software for staged reviews
Test workflows, permissions, invalid data, and integrations on the agreed devices. Involve representative users in acceptance testing.
Output: Test results and acceptance records
Prepare the release and transfer code, documentation, and access. Explain how the system is operated and the terms of ongoing support.
Output: Handover package and operating instructions
An application file is only part of a handover. The receiving team needs to know how the system runs, what it depends on, and who controls access. We define those deliverables when agreeing the scope.
Read the handover guideDeliverables, ownership, acceptance rounds, and post-delivery support are specified in the agreement for each project.
Stack
Practical guidance on writing a brief, choosing a platform, and reviewing a handover, so the first conversation has enough detail to make the next decision.
We consider workflows, user roles, integrations, existing data quality, and release criteria. Start with examples of the current work and what needs to change. Once the scope is clear, we set out the cost, delivery stages, and assumptions that affect the schedule.
We consider projects in any language or framework except COBOL, including web, mobile, desktop, and background services. Before agreeing the work, we review versions, dependencies, code rights, and test coverage. The tools on this website are examples, not an exhaustive list.
The agreement defines rights in the custom work and the source code, documentation, and accounts to be transferred. Third-party libraries and services retain their own license terms. We also identify external costs that remain after delivery.
Yes. Explain the current work, its users, the problems, and the outcome you need. Screens or documents with unnecessary personal information removed are useful. We can identify what is known, what needs investigation, and an initial scope to estimate.
The agreement sets out correction periods, maintenance scope, contact channels, and response arrangements. New features, changes to external services, and major upgrades are assessed against the work and impact involved.