What we build, and what we agree before starting.
Most work falls into two areas: websites and web applications, and first versions of products. Design, mobile work and engineering reviews sit alongside those. Each engagement has a defined scope, written down before work begins.
Websites and web applications
A clear, credible online presence, or a custom web tool where off-the-shelf software falls short.
Who it is for
Businesses that need a better customer journey, or dashboards, portals, workflows and integrations built around how they actually work.
What it can include
Discovery and structure of the site or application
Responsive interface design and implementation
Forms, integrations and deployment
Handover so the product can be run and changed without starting over
What we agree first
Whether copywriting, branding, SEO, analytics, content editing and ongoing maintenance are part of the project. For applications, also security, data migration, hosting and support.
MVP and product development
Turning a defined idea into a first version that people can use and you can learn from.
Who it is for
Founders and business leads who know what they want to test and want to spend as little as is sensible to find out.
What it can include
Defining the smallest useful scope
User flows and interface design
Building and deploying the first version
A plan for what to learn from early users
What we agree first
What the first version must prove, and what is deliberately left out. A first version tests an idea; it does not promise adoption or commercial success.
Alongside the build
These can be taken on their own or as part of a larger project.
UX and UI design
Clearer user journeys before or alongside the build: user flows, wireframes, interface design and implementation-ready specifications. This is design work, not formal user research or usability testing, unless that is agreed and carried out.
Mobile development
Mobile applications or mobile-friendly experiences where the business case supports them. Platforms, app-store accounts, device testing and release responsibilities are agreed before any quote.
Software consulting and engineering review
A focused look at architecture, code quality, performance, maintainability, technical choices or delivery risk. Scope, access and the format of the findings are agreed first, including whether implementation follows.
Prices and timelines
There are no fixed prices or delivery dates on this site, because they depend on scope. After a conversation and an agreed definition of what is in and out, you get a written proposal with deliverables, milestones, price and payment terms.
Have something in mind?
Share a few lines about the problem. That is enough to start.