Web apps, portals and internal tools
Give your team and customers one place to manage their work, with the right access for each person.
You might ask for
- A client portal
- A booking system
- An MVP in weeks
- A tool to approve requests
- A CRM that fits how we sell
Who it is for
- Teams coordinating work across spreadsheets, messages and shared files
- Businesses giving customers access to bookings, documents or project updates
- Founders turning a product idea into a first working version
What you get
- One place for the workflow your team or customers need
- Clear permissions for each role and sensitive action
- Less copying between your app and existing business tools
- A first version you can test before expanding the scope
Approach
Your team tracks requests in a spreadsheet, finds documents in email and asks someone else for the latest status. Customers need the same updates, but sharing the whole sheet gives them information they should not see.
We start by following one piece of work from arrival to completion. Together we identify who needs access, what they need to do and which steps belong in the first version. The written plan sets the scope, timeline, price and running costs.
We build the screens, accounts, permissions and connections around that workflow. Your team sees working progress and tries it with real scenarios, while a small first release helps us check the approach before adding more features.
We test access rules, important actions and the agreed integrations before launch. The app runs in your own accounts, with setup instructions, monitoring and a walkthrough so your team can use it and another developer can maintain it.
Deliverables
- A workflow map and written scope for the first version
- Screens and user journeys for the agreed roles
- A working app with accounts, permissions and the agreed features
- Integrations, release checks and a deployment in your own accounts
- Documentation and a team walkthrough
Technology
Next.js, React, TypeScript, Node.js, FastAPI, Django, Laravel, Ruby on Rails, PostgreSQL, Supabase, Firebase, Stripe, Clerk, Auth0, Retool, Appsmith
Ways to work together
- Model 01
Roadmap
A one to two week review of your users and workflow, ending in a written scope and a fixed quote for the app or portal.
- Model 02
Starter build
One app feature or a focused internal tool, with the agreed roles and integrations, live in two to four weeks.
- Model 03
Care plan
Monitoring, dependency updates, small fixes and improvements to your app each month.
Questions
Can we start with a spreadsheet or a rough idea?
Yes. We use your current workflow, spreadsheet or sketch to understand the problem. We agree on a small first version and what a useful result looks like before building.
Can customers and staff see different information?
Yes. We agree on the roles and what each person can view or change. Permissions are enforced by the system and tested with the scenarios your team uses.
Can the app connect to our existing tools?
We check the supported connections, permissions and limits of your tools during planning. The scope names the integrations included and any work that still needs a person.
Will we be able to work with another developer later?
Your code, repositories and hosting accounts belong to you. We provide setup instructions, documented decisions and a walkthrough so another developer can continue the work.
Start here
Tell me about the work that slows your team down.
A 20-minute call, no obligation. You leave with a written next step whether or not we work together. Plain language is fine; you do not need a technical brief.
Prefer to write? [email protected]
I read every message myself and usually reply within one business day.