A customer portal
Your clients sign in and see their own bookings, documents and balances. They stop emailing you to ask.
Grow
Cloud apps and customer portals
A cloud app is a small app built for one specific use case.
It opens in a browser and runs on our infrastructure. Your customers or your team use it to do one thing. We do not redo what already exists. If a tool out there does what you need, we name it and help you set it up. We build custom when the need is too specific for anything off the shelf, or when the off-the-shelf option is expensive overkill for the one thing you need.
01
What we build
A one-job internal app
One screen your team opens to do one task. It is built around the way that task already runs.
An API between two systems
Two systems that need to pass one kind of record to each other, connected directly.
A small tool your own customers use
When part of your service can be self-serve, we build that piece and your customers use it themselves.
02
How we decide to build
We look for the existing tool first
Most needs are already solved by something you can subscribe to. If yours is one of them, that is the advice.
We price the off-the-shelf option at your size
Your number of users, over a year. Per-user pricing often changes the answer.
We build when the gap is real
The need is too specific for anything off the shelf, or the existing option is expensive overkill for the one thing you want from it.
The scope stays small
One use case, built properly. More can come later if the first one earns it.
03
After delivery
The app runs on our infrastructure. Hosting, security updates, backups and small fixes are covered by the subscription. There is nothing for your team to host or update.
Your data stays yours. If you leave, it leaves with you in a format you can use.
04
Pricing
| What | Cost |
|---|---|
| Discovery: one call, our homework, a written solution and a price | Free |
| The build, at a fixed price | Quoted per job |
| Hosting, security updates, backups and small fixes | Covered by the subscription |
What moves the price: how many screens the app has, how many kinds of record it holds, and how many of your systems it reads from or writes back to. The build price is fixed in the proposal before anything starts.
The numbers, in one place
- Quoted per job as a fixed build price, with running costs covered by the subscription.
Questions
Questions
Sometimes that is the advice, and we say so. No-code covers a lot of portals. We build when the need does not fit those shapes, or when per-user pricing costs you more than a build does in the first year.
Yes. The app reads from and writes back to the systems you run today. We are not replacing your CRM, your customer database or your accounting tool. The app covers the one thing they do not do.
No. It runs on our infrastructure, which is how the hosting, the updates and the backups stay covered by one subscription instead of being billed by the hour. Your data is separate from that. It is yours, and you can take it out.
One use case. A portal that shows three things properly is worth more than a platform that does twenty things badly, and it costs a fraction to build.
The next step
Tell us the one thing you wish your customers or your team could do on a screen.
Leave a number and a good time to call, and we come back with the tool that already does it, or the case for building it.