Web DevelopmentWeb Development
Conversion-focused websites and web platforms built to reduce friction and support measurable growth.
App development for real workflows, not vanity features.
revamps scopes, designs and builds web apps, customer portals, internal tools and mobile apps around the process they replace: roles and permissions defined first, integrations tested with real data, usage tracked from release one, and a named team accountable after launch.
- Web apps, portals, internal tools, mobile
- Written scope for every release
- You own the code and the data
- Colombo team · Sri Lanka and international
Your team has grown. Your system is still a spreadsheet.
Orders arrive on WhatsApp, approvals sit in someone's inbox, and the real status lives in a sheet one person understands. Every new customer adds admin, errors reach the customer, and nobody can see where work is stuck. We build the app around that workflow and connect it to your tools. Now the process runs without the workaround.
Manual workarounds everywhere
Teams rely on spreadsheets, message threads and repetitive admin because there is no product built for the work.
Customers can't serve themselves
Bookings, orders and status checks go through calls and messages because there is no portal to do them in.
The idea has no first release
Scope is unclear, technical decisions are rushed and features pile up without a release plan that protects quality.
Tools that don't talk
Staff re-key the same data into each tool, and users jump between channels and forms to finish one task.
Screen. Rule. Record. Connection. One system.
Every app we build follows the same path. A person signs in with the right role, completes one task on a screen built for it, the rules check it, the record is stored and tracked, and connected tools act on it. The interface sits on top. This is what it is for.
From first call to a release your team uses.
Five steps, each closed by a sign-off, so the workflow and scope are agreed before development, and you review working software at every milestone, not slides.
Enquiry and reply
You tell us the process or the idea. We reply with the questions that matter and a time for a call.
Discovery and scope
Users, roles, workflow, data and integrations mapped, then a written scope: first release, platform, milestones.
Flow design
Screens, data movement, decision points and integrations, prototyped and signed off before development begins.
Iterative development
Milestones you review in working software, tested with real roles and real data, every integration exercised end to end.
Release and first 30 days
Into production with tracking verified and users trained, then fix what real usage shows first and plan the next release.
Screens are the part you see. The rules underneath do the work.
Six workstreams in every build. Depth changes by tier: how many roles and flows, how many systems it connects to, and how far the release plan reaches.
Scoping and product structure
Roles, use cases, permissions, states and delivery priorities, mapped before the build starts.
Flow and interface design
Screens designed around one task per role, prototyped and signed off before development.
Frontend and backend
The interfaces, services and data model the workflow needs, built to be extended rather than rewritten.
Integrations and tracking
Payments, CRM, messaging, accounting or your own APIs, tested with real data. Usage tracked from release one.
Testing and release
Quality checks, staging and launch planning in every milestone instead of left until the end.
Handover and ownership
Documentation, admin training, access to code, data and accounts, and a written list of what to build next.
Agree the bar before the build. Test it before launch.
- ≤ 2.5 s
Largest Contentful Paint
Sign-in and main task screens on a mobile connection, 75th percentile
- ≤ 200 ms
Interaction to Next Paint
How quickly a screen responds to a tap
- < 1.09%
User-perceived crash rate
Google Play's bad-behaviour threshold, for apps published on Play
Not every process needs an app. Here's when one pays.
We do our best work with teams who can name who will use the app and the work it replaces. If an off-the-shelf product or an automation covers it, we will say so on the first call.
A good fit if
You can name who uses it and the work it replaces. The workflow runs today on spreadsheets, paper or WhatsApp. One decision-maker reviews a milestone every week or two.
Not a fit if
You are choosing on the lowest quote. You want every feature in version one. A product you can buy already does the job. You need a website (Web Development) or existing tools connected (Workflow Automation).
Ask before you build. Get it in writing.
Do you work with clients outside Sri Lanka?
Yes. revamps is based in Colombo (UTC+5:30) and works in English. Scope, milestones and demos are written down and shared, so time zones change when we talk, not what gets delivered.
Can revamps build internal tools as well as customer-facing apps?
Yes. The same approach applies to internal workflow systems, partner portals and customer products when the process needs to be clarified and digitised.
Can you work alongside an existing engineering team?
Yes. revamps can take ownership of a defined product slice, architecture stream or implementation milestone while coordinating with internal teams.
Do we need a custom app, an off-the-shelf product or an automation?
If a product you can buy already does the job, buy it; we will say so. If people need a new screen to do the work, it is App Development. If the screens exist and only the hand-offs are manual, start with Workflow Automation. If you need a website, see Web Development.
Tell us the work it replaces. We'll scope the first release.
Four short fields, about a minute. Leave out anything confidential. We reply within 2 business days with the questions that set the scope and a time for a short call.
Prefer email? [email protected]
Release one is live. Keep it running and connected.
An app is not finished at release. Web Development builds the site that feeds it, Workflow Automation connects it to the tools around it, and Hosting and Maintenance keep it running. Each has its own page.
Workflow AutomationWorkflow Automation
Workflow automation for the work between your tools: enquiries routed to an owner, follow-ups sent on time, records kept in sync and reports that build themselves, with AI only where it pays, every flow monitored and a person on every exception.
HostingHosting
Managed hosting for websites and web apps, run as one measured layer of the system: uptime, server response and errors checked all month, backups restored to prove they work, and a named person who responds when something breaks and writes down why.
MaintenanceMaintenance
Maintenance for the site you already have: updates tested before they go live, security patches, the changes your team can't make, every form and link checked monthly and a written report, with set hours and a reply time on every plan.