Web apps that do the job
FlowConverts designs and builds web apps for UK businesses. A web app is software in the browser that lets people sign in and get something done. We plan the journeys, design the screens and build the working product, from portals and booking systems to marketplaces and internal tools.
- User roles, journeys and first-release plan
- Screen design and reusable components
- Front end, back end, accounts and data
- Payments, email and third-party integrations
- Security checks and handover in your name
(The problem)
Your process has outgrown spreadsheets and inboxes
Lots of businesses hit the point where the real work happens across email threads, shared spreadsheets and off-the-shelf tools that almost fit.
Every handover costs time, and customers feel the friction. A well-planned web app puts that work in one place.
Sound familiar? Customers email for things they could do themselves. Your team copies the same data between three tools. Off-the-shelf software forces your process into its shape. Or you've got a product idea and no team to build it.
(What you get)
The kinds of apps we build
(01)
Marketplaces and platforms
Two-sided products where people search, compare, message and book, like the Atlas freelancer platform.
(02)
Customer portals
Secure areas where customers sign in to see accounts, documents, orders or progress without emailing you.
(03)
Booking and request systems
Tools that take bookings or requests, check the details and route them to the right person.
(04)
Internal tools and dashboards
Admin panels and workflows that replace spreadsheets and give your team one source of truth.
(Is it for you?)
Do you need a web app, or a better website?
(A good fit)
- People need to sign in and do something, not just read.
- Your team runs a repeatable process across email, spreadsheets and several tools.
- Off-the-shelf software doesn't fit how you actually work.
- You have a product idea and want one team to design and build version one.
- The product and the website that sells it need to work together.
(Probably not)
- You mainly need to explain your services and win enquiries. Website design is the better route.
- An existing tool already does 90% of the job at a fair price.
- You can't yet say who the users are or what they need to get done.
- Every feature must be live by a fixed date before the scope is known.
(How it works)
Journeys first, then screens, then code
- (01)
Discover
Understand your users, the process the app replaces, the data involved and the technical constraints.
- (02)
Agree
Confirm first-release features, user roles, integrations, review rounds, ownership and exclusions. In writing.
- (03)
Design and build
Journeys to screen designs to a working app, with regular reviews of real, clickable progress.
- (04)
Test and launch
Security, accessibility, performance and journey checks, then launch and handover.
(Cost)
What a web app costs
No package price, because the work depends on what the app has to do. What shapes the quote: user roles and core journeys, features in the first release, data and integrations, and security or compliance needs.
We usually recommend launching the core journey first, then adding features once real people are using it. A first release is often a fixed project priced per scope.
For ongoing product work, the 3-month partnership is £4,500 a month: senior design and dev, requests one at a time, weekly progress, pause anytime.
(FAQ)
Good to know
What is a web application?
A web application is software that runs in the browser. A normal website mostly shows information. A web app lets people do things: sign in, search, save, message, book or manage data. Customer portals, booking systems, marketplaces and internal dashboards are all web apps, and people use them on a laptop or phone without installing anything.
How much does a web application cost?
There's no fixed price, because two apps with the same number of screens can need very different work. Cost depends on the user roles, core features, data, integrations like payments or email, and how much goes into the first release. Your proposal sets out the scope, exclusions and price before you commit to anything.
How long does it take to build a web app?
It depends on what's in the first release, how clear the requirements are and how quickly decisions get made. We won't quote a timeline before we understand those things. We usually recommend a focused first version that proves the core idea, then adding features once real people are using it. The proposal sets out stages and review points.
Do you design the app as well as build it?
Yes. We plan the journeys, design the screens and build the working app, so design and engineering decisions get made together. If the product also needs a public website to explain it and bring people in, we can design that too, as we did for Atlas. One team instead of three separate contracts and three sets of handovers.
Who owns the code and the data?
Ownership of the design, code, content and accounts is written into the proposal before you commit. As a rule, your domain, hosting, database and third-party accounts sit in your name, not ours. That way you can move to another team later without being locked in, and your customer data always stays under your control.
Can you add features after launch?
Yes. Most good web apps grow in stages. After launch we check that sign-up, core journeys, email and analytics work as intended. New features and fixes are scoped separately, or run through our 3-month partnership if you want steady progress. Either way, you're never tied into a retainer just to keep the app running.