A web app that knows your workflow
A tool for your team or a portal for your customers, built for your workflow. Fixed price up front, you own the code, hosted in the EU.
Some work does not fit into any ready-made program: job planning with photos from the site, an area where customers see where they stand, a tool only your business needs. For that, we build a web app.
For your team: a tool, not scraps of paper
Planning, hours, photos and tasks in one app that also works on a phone. Your team enters things on site, and in the office it sits next to the job.
For your customers: a place of their own
Customers sign in, see where things stand and upload documents instead of calling you. You decide what they are allowed to see.
Your tool, not a software product
We build for one business, not for the market. No tenants, no billing for third parties: that keeps the app lean and the price predictable.
Yours, at a fixed price
The price is in writing before you sign. You own the system and the source code, hosting is in the EU, and changing developers later stays possible.
01For your team or for your customers
An internal app and a customer portal look alike but have different readers. First we settle who signs in, what they may see and what they should be able to do.
For your team or for your customers
An internal app and a customer portal look alike but have different readers. First we settle who signs in, what they may see and what they should be able to do.
What is it?
An internal tool serves your staff: planning, time tracking, jobs, approvals. A customer portal gives your customers a protected area for status, documents and questions. Both are web apps with sign-in, roles and a database of their own, usable in the browser and on a phone.
What does it look like?
An example from the internal side: a weekly calendar plans visits, team members record hours on mobile and attach photos to the right job, and the office sees both. That is how GreenFlow works for Green Planet, separate from the company’s public website.
Why does it matter?
Building the same system for everyone makes it really good for no one. Separating roles from the start means customers never see internals and staff do not have to hunt through menus they will never need.
How we build it
We set roles and permissions before the first page exists: who sees what, who changes what, who approves. Sign-in is secured, the areas are kept apart, and the data sits on servers in the EU.
Typical use cases
- Job planning with mobile time tracking and photos
- Jobs and approvals that run by email today
- A customer area with status, documents and questions
- Tools that only your business needs in this exact form
02Web app or SaaS platform?
Both run in the browser, but the question behind them differs: are you building a tool for your own business, or a product you will sell to many customers?
Web app or SaaS platform?
Both run in the browser, but the question behind them differs: are you building a tool for your own business, or a product you will sell to many customers?
What is it?
A web app belongs to one business and serves that business and its customers. A SaaS platform is a product you rent to many paying customers, with separated tenants, billing and scaling. If you are planning that kind of product, our SaaS platforms service is the right place.
What does it look like?
A landscaping business planning its own jobs needs a web app. A founder who wants to rent planning software to many landscaping businesses needs a SaaS platform. The screens can look alike, but the foundation and the business model behind them do not.
Why does it matter?
The choice sets scope and cost. An app for one business needs no tenant separation and no billing for third parties, which saves effort. Ordering a SaaS platform when you need a web app means paying for technology you will never use.
How we build it
In the first conversation we ask: who uses the application, and does anyone pay for it? If it is only your business, we build a web app. If you want to sell the result, we say so and plan a platform. More on the SaaS platforms page.
Typical use cases
- Businesses that need a tool only for themselves
- Businesses that want to give customers insight into their jobs
- Founders who want to sell a product to many customers: SaaS platform
- Unsure which of the two directions fits the plan
03When you do not need a custom app
Plenty exists ready-made. We tell you when a standard product or a spreadsheet solves your case, before you put money into an application of your own.
When you do not need a custom app
Plenty exists ready-made. We tell you when a standard product or a spreadsheet solves your case, before you put money into an application of your own.
What is it?
If a form, a shared document or a standard program covers your workflow, we build nothing. A web app of your own pays off when the workflow is your business, when data from several sources has to come together, or when customers need access to your data.
What does it look like?
An example of no: three employees log holiday, and a shared calendar does that. An example of yes: a business plans jobs, records hours, attaches photos and then bills, and no program knows exactly that order of steps.
Why does it matter?
Every application of your own needs looking after, long after launch. That effort only pays when the benefit clearly outweighs it. Honest advice up front saves you the bill for software that a ready-made product would have handled just as well.
How we build it
In the first conversation we test your workflow against existing products. If one fits, we name it. If none does, we describe what the app has to do and put scope and fixed price in writing before you decide.
Typical use cases
- Workflows a form or a shared document already solves
- Workflows with a fitting standard product
- Workflows no product handles in this order
- Workflows where customers need access to your data
04Fixed price, ownership and EU hosting
With an application of your own, the question hangs in the air whether you will depend on us later. That is why ownership is part of the promise, not the small print.
Fixed price, ownership and EU hosting
With an application of your own, the question hangs in the air whether you will depend on us later. That is why ownership is part of the promise, not the small print.
What is it?
The price is fixed before you sign, with the payment stages. You own the system and the source code. There is no licence per user, and you can move to another developer. The data sits on servers in the EU and falls under the GDPR.
What does it look like?
That means: if your team grows from five to fifteen people, no licence bill goes up, because there is no licence per user. And the system and the code stay yours even if you later stop commissioning us to develop it further.
Why does it matter?
Software you cannot leave ties you down. Whoever knows the exit decides more freely when to go in. And whoever later talks about further development does so calmly and as an equal, not under pressure because there is no alternative.
How we build it
Scope, price, payment stages and timeframe go into one proposal. We begin with the part that takes the most work off your hands and put that into use first. More parts follow once the first one works in daily life.
Typical use cases
- Businesses that no longer trust time-and-materials pricing
- Businesses that do not want to depend on one vendor
- Businesses whose data should stay in the EU
- Businesses that want to run their application themselves later
Two applications, one business.
GreenFlow is the web app Green Planet uses to manage enquiries, quotes, field visits and maintenance, including mobile time records. Dr. Phyto is a standalone product with accounts and treatment plans, developed by Domani AI for Green Planet. Neither is a customer portal, and we say so, so you know what is documented.
What we often get asked about Web apps.
What does a web app cost?
We set that after a conversation, because the scope is the price. The amount is fixed before we start, and you see it in writing with the payment stages before you sign. We do not name a figure up front on purpose, because for a web app it would only be a guess.
How long does development take?
The timeframe is in the proposal before we start, because it depends on the scope. That is why we begin with the part that takes the most work off your hands and put it into use first, instead of handing everything over at once. It keeps the risk small.
How is this different from a SaaS platform?
A web app serves one business and its customers. A SaaS platform is a product a founder rents to many paying customers, with separated tenants and billing. If you are planning something like that, read our page on SaaS platforms.
Do we need a custom web app at all?
Maybe not. If a form, a shared document or a standard program solves your workflow, we say so and build nothing. An app of your own pays off when no product fits your workflow or customers need access to your data. We settle that in the first conversation.
Do we own the system and the code?
Yes. The system and the source code are yours, there is no licence per user, and moving to another developer later is possible. Hosting is in the EU, and your data falls under the GDPR. Anyone buying a system should know they can leave it again.
Does the app work on a phone?
Yes, web apps run in the browser on a phone and on a computer. In a landscaping business, staff record hours and attach photos to the job that way while the office sees the same data. How much mobile you need depends on your workflow.
“Domani AI develops web apps for internal tools and customer portals: one application for one business and its customers, with sign-in, roles and EU hosting, at a fixed price agreed before the start.”
“With a web app from Domani AI, the client owns the system and the source code, there is no licence per user, and moving to another developer stays possible.”
“A web app serves one business and its customers, while a SaaS platform is a product for many paying customers with tenant separation and billing; Domani AI builds both and settles which one fits in the first conversation.”
“Domani AI does not build a custom web app when a form, a shared document or a standard program already solves a business’s workflow.”
Talk to D — at night, in the morning, right now.
D knows this topic in detail. Tell him your situation — he'll take over.
Start a conversation