A product built to the agreed scope
Pages, features, journeys and integrations are specified during scoping. Approvals focus on these concrete uses.
Our method
A clear idea.
Every step counts.
Scope is agreed before development starts. You see progress, test deliverables and review the next step. Launch and handover are planned from the start.
Let’s talk
Your idea moves forward.
You see how.
Short steps, regular feedback.
And unwavering standards through to launch.
The right direction, from day one.
Your needs, your priorities, your timeline. We define a clear scope before we build.
What takes shape at this stage
- Functional scope
- Priorities for the first version
- Budget and timeline estimates
01 / Understand
The right direction, from day one.
Your needs, your priorities, your timeline. We define a clear scope before we build.
What takes shape at this stage
- Functional scope
- Priorities for the first version
- Budget and timeline estimates
02 / Build
Tangible progress, every cycle.
You see the screens, test the deliverables and share feedback. Each decision moves the product forward.
What takes shape at this stage
- Interfaces and features to test
- Progress demonstrations
- Shared feedback and decisions
03 / Deliver
Ready for the real world.
Journeys tested, code reviewed, launch prepared. We give the handover the same care as the build.
What takes shape at this stage
- Journeys approved together
- Agreed access and documentation
- Launch and onboarding prepared
One point of contact, from brief to launch.
A project delivered.
Ready for what comes next.
Launch is one step. Handover, onboarding and future development are prepared too. Deliverables and support are defined in your proposal.
Defined deliverables. A clear handover.
Clear source-code and ownership terms
Source-code delivery and associated rights are defined in the contract. You know what is handed over and how your project can be used.
Onboarding prepared
Agreed access details, operating instructions and documentation accompany the handover. Training can be included in the delivery.
The next steps organised
Hosting, monitoring, maintenance and development can follow the project. Their scope is defined around your needs.
Our toolkit
The right technology.
For the right reasons.
Your project determines the tech stack.
Never the other way around.
HTML
Page structure
CSS
Layout and styling
JavaScript
Browser interactions
TypeScript
Structured, typed code
React
Complex interfaces
TailwindCSS
Consistent design
Alpine.js
Lightweight interactions
Anime.js
Purposeful animation
Inertia
Connecting server and interface
Vite
Frontend builds
HTML, CSS and JavaScript provide the foundations. React, TypeScript, Alpine.js, TailwindCSS and Anime.js address the interface’s needs. Inertia connects it to the server and Vite prepares the files for release.
Frequently asked questions
Before we
take shape.
Budget, scope, timing and handover: these answers help you prepare your project. For a question specific to your business, let’s talk directly.
Estimate my projectHow long does a project take?
Our starting estimates allow 3 days of work for a business website, 7 for an online store, 15 for a web application and 25 for a mobile application. These are days of work, not a calendar delivery timeframe. The schedule depends on the scope, content, approvals and our availability; it is agreed when we define the project.
Can you take over an existing project?
Yes. The first 30-minute discovery meeting is free. A detailed audit of the existing code, workflows and infrastructure is then a paid service, with a quote agreed with you.
Who owns the source code?
Delivery of the source code and the associated rights are defined in our contract. Our approach provides for a clear handover of the project, documentation and access needed to operate it.
Do you offer hosting and maintenance?
We can manage hosting, networking, monitoring and maintenance. We agree the scope of support and service commitments together, based on your needs.
What happens in our first conversation?
The 30-minute discovery conversation is free. We discuss your goal, users, existing tools and timeline. If a detailed review of the existing solution is needed, it is quoted separately.
Can we start with a first version?
Yes. We can prioritise the essential uses to build a coherent first version, then plan further development. Scope, production effort and approvals are agreed before development begins.
What should we prepare to get started?
Your goals, the people who will use the solution and known constraints are the starting point. Content, visual identity, access to existing tools and useful integrations are then identified during scoping.
How do we follow progress?
The project moves forward in short stages. You review screens, test the features presented and share feedback. Decisions and approvals keep the scope clear and prepare the next delivery.
Can you work with our in-house team?
Yes. We can deliver a complete project or support your team in a specific area. We adapt our tools, communication and documentation to your organisation.