Applications
When the work needs more than pages.
Web applications and portals for customers, staff or partners when a website is not enough.
- Good for
- Businesses needing this done properly, once
- Includes
- 4 agreed deliverables
- Pricing
- Quoted on scope, agreed before work starts
What this usually looks like
The problem
A process lives in spreadsheets, emails and manual double-entry. Customers or staff need to log in, submit, track or manage something the current website cannot handle.
How we approach it
We scope the workflow first, then design and build a web application around it — with the screens, roles and data that process needs.
What you receive
- Workflow and role mapping
- Interface design for each key screen and state
- Build of the agreed application scope
- Staging environment for testing before release
Deliverables are confirmed in your proposal. Anything outside that list is quoted before it starts.
What we need from you
- 01Describe the current process accurately, including exceptions
- 02Nominate people to test with realistic data
- 03Confirm the agreed scope before build starts
Pricing approach
Applications are quoted after a scoping stage, because the amount of work depends on roles, data and exceptions. We stage delivery so you can see progress early.
Cost and scope
What this typically costs, and what changes it
Applications are quoted after a scoping stage, because the amount of work depends on roles, data and exceptions. We stage delivery so you can see progress early.
Published rates and package inclusions are still being confirmed. Anything not confirmed is quoted in writing rather than estimated here — no totals are invented to make the page look complete.
Typical engagement
- Quoted as
- Fixed scope, agreed before work starts
- Review points
- Named in the proposal
- Next step
- A short call, then a written scope
Related work
Where this work appears
- QNP Group
Digital commerce · 2025
- BFS Plastics
Digital commerce · 2026
Contribution and engagement details for each project are being confirmed. We do not publish testimonials or results we cannot evidence.
Process
How a project runs
The same checkpoints apply across services, with review points agreed for your scope.
Review
We look at your business, customers and what the website or system needs to achieve. Goals and priorities Opportunities to improve
Plan
Priorities become a sitemap, content requirements and technical approach. Sitemap and feature scope Agreed schedule and review points
Design
You review desktop and mobile layouts and approve the direction before build. Desktop and mobile layouts Design approval checkpoint
Build
The agreed design is built. A staging preview lets you review before going live. Working staging preview Content and functionality review
Launch
Pages, links and forms are checked. Where a CMS is included, your team gets a walkthrough. Launch checks and deployment Editor handover (if CMS included)
Staging previews
Review the working site or application before it goes live.
Handover
Editor walkthrough where a CMS is included in the project.
Support after launch
Support and maintenance terms are agreed in your proposal (to be published).
Good to know
Frequently asked
questions.
Tell us what is not working and what you would like instead. We reply by email, then arrange a discovery call if it looks like a fit.
Other studio services
Developer? Explore the UI Library
The UI Library is a different audience: reusable Payload CMS blocks and React components you install in your own project. It is not a finished website service.
