Design plus development
- Flows and UI first, then the build of the screens you signed.
Custom web applications
Custom web applicationsCustom web apps and client portals, with design included or from your signed screens.
A scoped product in the browser: a client portal, an internal tool, or a custom app on a stack you name. You keep the client. We never contact them. Bring approved screens, or put UI in this order.
We can build with
- WordPress
- Wix
- Squarespace
- Webflow
- Shopify
- React.js
- HTML
What the web app is for
This is software, not a marketing website. Pages people log into, data they can change, and roles you define in the brief.
- 01
A product in the browser
Portals, dashboards, and tools with accounts, not a brochure site.
- 02
Design plus development, or development only
If the screens are already signed, we build them. If not, UI sits in this quote as its own phase.
- 03
A stack you can keep
The quote names the runtime, the host, and where the repo lives. You keep that access.
- 04
Roles and data, written down
Who can see what, and which records the app stores, sit in the brief before we build.
- 05
You remain the studio
Logins, handover, and the admin training go through you.
Two ways to order it
The difference is whether screens are already approved. The engineering phase is the same idea either way.
Development only
- We implement the files you bring.
- Gaps in the spec are quoted before we invent screens.
How it runs
From the jobs to a portal you can hand over
You sign screens before production. Quality check is done in Europe.
How revision rounds work
The jobs and roles in the brief, with the quoted design and build rounds.
A new module, a second product, or a rewrite of signed screens is a new quote.
What we do, and what we need from you
A portal waits on roles, data rules, and logins. This is the split.
| Task | Your agency |  |
|---|---|---|
| We scope jobs, roles, and whether design is included. | ||
| We build the signed screens on the named stack. | ||
| We give you staging, then handover notes and repo access. | ||
| We never contact your client. | ||
| Who logs in, what they must finish, and which records the app stores. | ||
| Approved screens, or a decision that UI is in this order. | ||
| Hosting and domain decisions, plus any systems we must connect. | ||
| Someone who can test the staging URL and who speaks to the client. |
Not a marketing website
Public sites sit on Web Design. This page is logged-in software: portals, dashboards, and tools with accounts, roles, and records people can change. A brochure site, even a large one, is a different order.
AI-assisted builders are a different page
If the product belongs on Cursor, Bubble, or Lovable as an AI-assisted build, that is AI Apps & Websites. This page is a scoped web app on a stack you name and keep, not a two-to-eight-week builder engagement.
After launch
Small tickets can sit on Ad-hoc Development Support. A named person every week is Dedicated Resources. Neither of those replaces the first handover: repo access, staging, and the notes your team needs to put it in front of the client.
Agencies often add these extra services
From the blog
Notes that sit next to this work. All notes
Web Design & Dev
Progressive Web Apps
What progressive web apps are, how they compare with native apps and when a PWA is the right choice for a client's project.
2 min read
Frequently asked questions
Agencies that need a scoped web app or portal under their own name, with or without design in the same order.
Ready to brief a web app?
Name the jobs and the roles. We design if you need it, then we build, under your name.