Customer portals
Accounts, orders, bookings and documents in one place your customers can reach from any browser, connected to the systems you already run.
First releasefrom $25,000
Software shaped around the way you work
Customer portals, internal tools and mobile apps, designed with the people who will use them and built by a senior team. Every project begins with a two week discovery sprint and a fixed price for each stage.
2 weeksof discovery first
Fixed priceper stage, in writing
Yourscode, accounts and data
- Web applications
- Apps for phones and tablets
- Security review before every launch
- One team from scoping to support
What we build
Prices are starting points for a typical first release. The discovery sprint turns them into a fixed quote for your project.
Internal tools and dashboards
The spreadsheet that runs the business, rebuilt as a proper tool with permissions, history and reports the whole team can trust.
First releasefrom $15,000
Mobile apps
Apps for phones and tablets that work offline in the field and sync when the signal returns, published to both main app stores.
First releasefrom $35,000
Integrations
Accounting, stock, payroll and booking systems connected so data is entered once and every system agrees on the numbers.
Per connectionfrom $6,000
Rescue and modernising
Software another team started or nobody dares to touch, audited first, then made safe with tests before new features go in.
Two week audit$4,000
Support after launch
Security updates, uptime monitoring and a set number of hours each month for small changes and questions from your staff.
Monthly planfrom $900
How a project runs
Each stage has its own fixed price, and you can stop after any of them with everything produced so far.
Discovery sprint
Two weeks of workshops with the people who will use the software, ending in a clickable prototype and a written scope.
Design and plan
Screens are designed and tested with real users, and the build is split into releases with a fixed price for each.
Build in two week cycles
Every second Friday you see working software on a test site and choose what the team builds next.
Launch and handover
A security review, data moved from the old system, staff trained, and the code handed over with its documentation.
Three ways to work with us
Most clients start with a discovery sprint. Some keep a team on a monthly basis once the first release is live.
Discovery sprint
fixed price$6,500
- Workshops with your staff and customers
- Clickable prototype of the main screens
- Written scope with a fixed price per stage
- Yours to keep, even if another team builds it
Fixed scope build
from$28,000
- Design, build, testing and launch
- Working demo on a test site every second Friday
- 60 days of fixes after launch included
- Price fixed per stage before work starts
Monthly team
a month, from$12,500
- For products that keep growing after launch
- Planning with you every two weeks
- Scale the team up or down each month
- Same people from month to month
Each stage is invoiced at its start, and payment is arranged directly with us. Prices exclude any sales tax that applies where you are.
Which kind of build fits the problem?
Not every problem needs an app in the stores. These are the patterns we see most often, and what we usually suggest.
| What is happening now | What we usually build | Typical first release |
|---|---|---|
| Staff copy data between spreadsheets every week | An internal web tool with roles and reports | 8 to 12 weeks |
| Customers phone or email to book, reorder or check status | A customer portal on the web, linked to your systems | 10 to 14 weeks |
| Field staff work where the signal drops | A mobile app that works offline and syncs later | 12 to 18 weeks |
| Two systems hold different versions of the same numbers | An integration so data is entered once | 3 to 6 weeks |
| An old system works but nobody can change it safely | An audit, then a rebuild in stages beside the old one | Audit in 2 weeks |
Senior people from first workshop to launch
The people who scope your project are the people who build it. You talk directly to the developers and the designer, not through a chain of account managers, and every question gets an answer from someone who has read the code.
We write automated tests as we build, review every change before it is merged, and keep a plain written record of each decision, so a new developer could pick up the work years from now.
- Code in a repository you own from the first day
- Automated tests run on every change
- Accessibility checked against recognised guidelines
- Data stored in the region you choose
Inside recent projects
Client names stay private, so these photos show the work rather than the logos: workshops, prototypes and software in daily use.
What clients say (example reviews)
The discovery sprint gave us a clickable prototype and a fixed price before we committed to anything. The warehouse team still uses the app on every shift.
They took over an app another agency had left half built, wrote tests around the fragile parts first, then shipped the missing features without breaking the old ones.
Every second Friday there was a working demo on the test site. Nothing about the build was a surprise, including the final invoice.
Questions before a project starts
Who owns the code and the designs?
You do, from the first day. The code lives in a repository under your account, and hosting, domains and app store listings are set up in your name, so you can change suppliers at any time.
How do you work out the price?
Every project starts with a two week discovery sprint at a fixed $6,500. At the end you receive a written scope and a fixed price for each stage, and you decide whether to go ahead with us, with another team or not at all.
Can you take over software another team started?
Yes. A rescue starts with a two week audit of the code, the hosting and the open issues. We report what is sound, what is risky and what it would cost to fix before anything is changed.
Do you build apps for phones as well as the web?
Yes. Most of our mobile apps share one code base across both main phone platforms. When a web app that works well on phones would do the job, we say so, because it costs less to build and to maintain.
Where is the data stored?
In a cloud region you choose, usually the one closest to your customers. Privacy and data protection rules vary by country, so we list the ones that apply to your project during discovery and design around them.
What happens after launch?
Every build includes 60 days of fixes for anything that does not work as agreed. After that, a support plan from $900 a month covers security updates, monitoring and a set number of hours for small changes.
Request a quote or a call
Tell us what the software should do, who will use it and when it needs to be ready. A product lead reads every request and replies within one working day with questions or a time for a call.
- A reply within one working day
- Fixed price per stage, agreed before work starts
- Confidentiality agreement signed first if you prefer
Talk to the studio
Phone the studio on weekdays, or write to the projects inbox at any hour; a product lead answers by the next working day.
Reach us
Studio in the city centre, working with clients in person and by video across time zones
Studio hours
| Monday to Friday | 09:00 to 18:00 |
| Calls with other time zones | By arrangement |
| Saturday and Sunday | Closed |
Working across time zones
Clients in other countries work with us by video, with calls placed inside their own working hours. Workshops can also be held at your offices, with travel quoted before we book it.