01
Development
Custom Software Development
Purpose-built applications that model your real operation (your data, your rules, your terminology), owned outright by you.
From$3,200
Software Development · Service 02
Web Application Development
Portals, dashboards and multi-tenant platforms that run in any browser: fast, accessible and secure, on code and hosting you own.
Starting from
$3,000
- Discipline
- Software Development
- Shortest timeline
- 5 to 8 weeks
- Clients
- Businesses, organizations & founders
- Delivery
- Remote, worldwide
What this service is
Everyone you work with already has a browser open. A well-built web application meets them there: nothing to install, nothing to update, and the same current information on every screen.
Web application development is the engineering of software that runs in the browser: client portals, partner extranets, internal dashboards, booking and ordering systems, and subscription platforms you sell to other companies. Unlike a marketing website, a web application has accounts, permissions and data that changes all day. People depend on it to get their work done.
The difference between an application people put up with and one they're glad to use is in the details. Pages respond quickly on a mid-range phone. Forms work with a keyboard and a screen reader. Sign-in uses the accounts your staff already have. Customer data stays separated and secure. We treat all of that as part of the build from the first sprint, not as polish for the last one.
Problems we solve
The situations that bring people to us
A web application is usually the right fix when you recognize one of these.
The situation todayWhat changes
Clients email or call your team for updates they could look up themselves
A secure portal where clients check status, download documents and manage their own details
Staff in the field fall back to paper because the system only works at a desk
A responsive, installable web app that works on phones and tablets, even on a weak signal
People juggle a separate password for every tool, and departing staff keep access for weeks
Single sign-on through your identity provider, with access removed in one place
Pages crawl on mobile, and users abandon forms halfway through
Fast pages, held to a performance budget and tested on real devices and networks
You want to sell your software to other companies, but it was built for one
A multi-tenant platform that keeps each customer's data, users and settings separate
A large prospect asks about accessibility and security, and you have nothing to send
Accessibility test results and documented security controls, ready for procurement questionnaires
What you get
Deliverables
Not every engagement includes every item. Your proposal lists exactly what's in scope, and what isn't.
-
01
User roles and journey maps
Who signs in, what each type of user needs to get done and the shortest path to it, agreed in writing before design starts.
-
02
Design system and responsive screens
Reusable components, type and color styles, and production screens designed for phone, tablet and desktop from the start.
-
03
Accessible front end
Semantic markup, keyboard navigation, visible focus and screen reader testing, built and checked against WCAG 2.2 AA.
-
04
Sign-in and single sign-on
Email sign-in with multi-factor authentication, passwordless links, or SSO through Microsoft Entra ID, Google Workspace or Okta.
-
05
Back end and documented API
Server-side rules, the database and an API the browser talks to, documented so a mobile app or partner integration can use it later.
-
06
Accounts, teams and tenants
Invitations, roles, organization settings and, for multi-tenant platforms, data separation enforced at the database level.
-
07
Security, performance and browser testing
Checks against the OWASP Top 10, dependency scanning, load tests, and every release tested on the browsers and devices you've agreed to support.
-
08
Hosting, monitoring and handover
Infrastructure in your own cloud account, automated deployments, uptime and error alerts, and documentation your team can run with.
Visual model
How a web application is put together
How the pieces typically fit together on this kind of engagement.
ClientsSelf-service portal
Your teamAdmin and dashboards
PartnersLimited, scoped access
Browser front endResponsive, accessible, installable
Sign-inSSO, MFA and session control
Application APIBusiness rules and permission checks
DatabaseSeparated by tenant
File storageUploads and PDFs
Background jobsEmail and exports
MonitoringUptime and errors
Common use cases
Where this work usually applies
Practical patterns rather than industry labels. The shape of the problem matters more than the sector.
-
Use case 01
Client and customer portals
Account status, invoices, documents and support requests in one signed-in place, so routine questions stop landing in your team's inbox.
-
Use case 02
Partner and supplier extranets
Dealers, resellers or suppliers place orders, check stock and download price lists, each seeing only their own accounts.
-
Use case 03
Operational dashboards
Live figures from your own systems, with filters, drill-downs and scheduled exports for the people who act on them.
-
Use case 04
Multi-tenant SaaS platforms
Software you sell by subscription, with self-serve sign-up, team invitations, plan limits and each customer's data kept apart.
-
Use case 05
Booking and ordering systems
Availability calendars, reservations, deposits and reminders, so customers book in a few clicks instead of a chain of emails.
-
Use case 06
Field and offline web apps
Progressive web apps that install from the browser, keep working without a signal on site and sync when the connection returns.
Our approach
How we handle this kind of work
The parts of our method that matter most for web applications.
- 01
Test on the devices your users actually carry
We measure speed on mid-range phones and throttled connections, not just a fast laptop on office Wi-Fi, because that's where slow pages show up first.
- 02
Build accessibility into every component
Keyboard support, focus order, contrast and screen reader labels are part of each component's definition of done. Retrofitting them later costs far more.
- 03
Check permissions on the server, every time
Hiding a button isn't security. Every request is checked against the user's role and account before any data leaves the database.
- 04
Put browser support in writing
We agree which browsers and devices you support (by default, recent versions of Chrome, Edge, Firefox and Safari) and test against that list before every release.
- 05
Watch it in production from day one
Error tracking, uptime checks and performance monitoring go live with the application, so problems are spotted before users report them.
Project stages
From first conversation to delivery
Each stage has a defined output and a review point, so you always know where the work stands.
How our process works-
01
Research
Interviews with each user group, journey maps, an agreed browser and device list, and a written scope with a fixed quote.
-
02
Prototype
A clickable prototype tested with real users, then a design system and final screens for every screen size.
-
03
Foundations
Hosting, sign-in, roles and the deployment pipeline set up first, so every feature after that ships straight to a live preview.
-
04
Features
Screens and API built together, one user journey at a time, and demonstrated on staging at the end of each sprint.
-
05
Hardening
Accessibility audit, security review, load testing and cross-browser checks against the agreed support list.
-
06
Launch
Domain, certificates, monitoring and alerts in place, a staged rollout to users, then a support plan sized to how often the application changes.
Capabilities
What we bring to this work
Only the capabilities that matter for this service, and nothing we wouldn't actually recommend.
Interface
- Responsive layouts from phone to desktop
- WCAG 2.2 AA accessibility
- Progressive web apps and offline mode
- Design systems and component libraries
- Live updates without page reloads
- Data tables, charts and filters
Platform
- Single sign-on with SAML and OpenID Connect
- Multi-factor and passwordless sign-in
- Multi-tenant data separation
- Role-based permissions
- Documented REST and GraphQL APIs
- File uploads and document storage
Operations
- Hosting on AWS, Azure or Google Cloud
- Content delivery and caching
- Automated deployments
- Error tracking and uptime alerts
- Performance budgets and monitoring
- Backups and disaster recovery
Delivery and engagement
Typical timelines
Timelines depend on the number of user roles and screens, single sign-on and integration requirements, and how quickly your team reviews designs and tests releases. Every proposal includes a dated schedule.
Focused portal or dashboard5 to 8 weeks
Business application with several user roles3 to 5 months
Multi-tenant SaaS platform5 to 8 months, launched in stages
Who it's for
Typical clients for this work
We work with companies, organizations and individuals. The requirement matters more than the size of the buyer.
Businesses
- Service firms whose clients want to look up their own information
- Distributors and manufacturers working with dealers and suppliers
- Companies selling to enterprises that ask about SSO, accessibility and security
- Teams replacing a desktop or spreadsheet tool with one everyone can reach
Organizations
- Nonprofits running member, donor or volunteer portals
- Schools, training providers and associations offering online access
- Public bodies and regulated providers with accessibility obligations
Software teams and founders
- Founders turning a proven service into a subscription platform
- Product companies adding a customer-facing web app to an existing system
Related services
Often commissioned alongside this
04
Development
API & Systems Integration
Connect your CRM, ERP, accounting, store and payment systems so data moves on its own, mapped in writing, retried safely and monitored.
From$2,500
05
Development
MVP & Digital Product Development
The smallest real product that tests your riskiest assumption, with accounts, payments and analytics in place, on code that can grow if it works.
From$3,200
Service FAQ
Questions about web applications
Could a low-code tool do this instead?
For some internal tools, yes. If the job is mostly forms and lists for a small team, Retool, Glide or Microsoft Power Apps may be cheaper and faster, and we'll tell you so. Custom development is the better choice when the application faces customers, carries your brand, needs fine-grained security or will grow into a product.
Should this be a web app, a mobile app, or both?
For most business software, start with a responsive web application: one codebase, instant updates and no app store review. A progressive web app can be installed on a phone's home screen and work offline. Native apps earn their extra cost when you need background location, Bluetooth devices or app store discovery, and the API we build can serve one later.
Can people sign in with the accounts they already have?
Yes. Staff can use their work login through Microsoft Entra ID, Google Workspace, Okta or any provider that supports SAML or OpenID Connect, and can't sign in once that account is disabled. Customers can use email, passwordless links or social accounts, with multi-factor authentication where the data warrants it.
How do you handle security?
As part of the design, not as a final check. Permissions are enforced on the server, data is encrypted in transit and at rest, dependencies are scanned on every build, and the application is reviewed against the OWASP Top 10 before launch. If you need an independent penetration test, we'll prepare for it and work through the findings with you.
What does the $3,000 starting price cover?
A focused web application built around one main user journey, such as a client portal or a reporting dashboard: a handful of screens, standard email sign-in and data from one source. Single sign-on, multi-tenancy, complex permissions and integrations add to the scope. You'll receive a fixed quote against a written scope before you commit.
Starting from
$3,000
Final pricing depends on the number of user roles and screens, sign-in requirements, integrations and hosting needs. You'll receive a fixed quote against a written scope before any commitment.
Have a project in mind?
Tell us what you're trying to achieve. We'll come back with a clear view of the scope, the approach and the cost, and if we're not the right fit, we'll say so quickly.