Focused project
One clearly defined piece of work with an agreed scope and finish line.
- Good for
- A single assistant, workflow, landing page or tool.
Includes
- Short discovery and written scope
- Build, testing and launch
- Hand-over notes
Service
Custom tools and integrations
When a spreadsheet is no longer enough and a large system is too much: internal tools, client portals, calculators and integrations built for one job.
Problems this solves
- A critical process lives in a spreadsheet that only one person understands.
- Two systems you rely on do not share data.
- Customers or staff need a simple tool (a calculator, a status page, an intake form) that no product offers.
What we typically deliver
- A short specification agreed before building: users, data, screens, limits.
- The tool or integration, deployed on infrastructure you own.
- Sign-in and permissions where needed.
- Documentation and access handed over to you.
How it can work
A small purpose-built tool or integration that fills the gap and stays maintainable.
Define the job
One problem, the people who have it, and what success looks like.
Prototype
A clickable or working first version you can react to.
Build and connect
Connected to your data and tools, tested with real cases.
Hand over
You own the code, the accounts and the documentation.
Is it a good fit?
A good fit when
- The need is specific and existing products almost fit.
- You want to own the result and keep it simple to maintain.
Probably not the right fit when
- An existing product already does the job well enough. We will tell you if so.
How we work
From first conversation to support
Small, visible steps. You see working pieces early and decide what comes next.
Discover
We look at how the work happens today, where it gets stuck and what a good result would look like for you.
Define
We agree what to build first, what is out of scope, and how we will both know it works.
Build and test
Short iterations using real examples from your business. You see working pieces early.
Launch and support
We go live with a clear hand-over, then adjust as real use shows what to improve.
Ways to work together
Engagement options
We agree scope and price for each piece of work after a first conversation. There are no fixed packages.
Phased build
A larger goal split into phases, each one usable on its own before the next begins.
- Good for
- Connecting several processes, or a website plus automation and an assistant.
Includes
- A roadmap with agreed phases
- A review at the end of each phase
- Freedom to stop or change direction between phases
Ongoing support
Regular care for what we have built: monitoring, small changes and improvements.
- Good for
- Assistants and automations that need tuning as your business changes.
Includes
- An agreed monthly allowance of time
- Monitoring and fixes
- Suggestions based on real use
Questions
On infrastructure in your name, chosen for the tool’s needs and your budget. We explain running costs before building.
Yes. We write, design and test in both, including right-to-left layouts and replies that read naturally in each language.
It depends on scope, so there are no fixed packages. After a first conversation we send a written scope and price for the first piece of work.
Start a custom tool project
Describe what you have today and what you want to change. A short message is enough to start.
Other services
AI agents
- Problem
- Customers wait for answers and the same questions keep landing in your inbox.
- Outcome
- An assistant that answers common questions from approved content, captures the details you need and hands over to a person when it should.
Business automation
- Problem
- Work moves between tools by copy and paste, and things get missed.
- Outcome
- Connected workflows that capture, route and follow up on their own, with a clear record of what happened.
Websites and landing pages
- Problem
- Visitors cannot tell quickly what you do or what to do next.
- Outcome
- A fast, clear site in two languages that explains what you offer and makes the next step obvious.