Services Development
Web apps
Browser-based applications with accounts, data and workflows, built and tested as one working product.
At a glance
- Includes
- Front end, back end, database, accounts and permissions
- Works with
- Your existing systems, data and design files
- Delivered as
- Source code in your repositories, running in your own hosting
- Starts with
- A review of the workflow the app has to support
Fit
Is this right for you?
Usually the right call when one of these sounds familiar.
Work run from spreadsheets
Several people edit the same files and lose track of the latest.
A manual process with many steps
Requests move by email, chat and memory.
Customers need their own login
They should see their own data and nothing else.
An internal tool that has outgrown itself
It was built quickly and now slows the team down.
Not the right service? Mostly pages edited by staff: CMS websites. A shop with a basket and checkout: E-commerce.
Scope
Scope and what you get
Each piece of work has a matching thing you receive.
- What we do
Workflow mapping
We write down who does what in the process and agree what the app must handle first.
What you receiveA scoped plan
The screens, roles and rules agreed in writing before building starts.
- What we do
Front end and back end
Screens and server logic are built and tested together, in short releases you can try.
What you receiveA working application
A product you can use in a browser, released in stages for your review.
- What we do
Accounts and permissions
Sign-in, roles and access rules so each person sees what they should.
What you receiveAccess you control
Roles that you can change and a record of who can reach what.
- What we do
Tests and deployment
Automated tests and a repeatable release process are set up with the code.
What you receiveA release you can repeat
A documented way to publish a change, with tests that run before it goes out.
Use cases
Relevant use cases
Practical situations where this service is put to work. Open a card to see how it applies.
A portal for customers or partners
A secure area where people sign in to see their own orders, documents or requests.
- Sign-in and roles set for each type of user
- Their own data shown, and only theirs
- Requests tracked from first message to close
Replacing a spreadsheet process
A shared application that takes over a workflow that lives in files and email.
- Existing data brought across and checked
- Steps, approvals and status kept in one place
- Reports staff can open without asking for a file
An internal tool for staff
A focused tool for a team, built around the way they already work.
- Screens designed around the daily task
- Roles for managers and regular users
- Connected to the systems already in use
Sample use cases, drafted as placeholders. The Plethora team confirms the final list.
Process
How it works
Each stage is agreed with you as we go. Each shows what we do and what we need from you.
Understand
We doWe map the workflow, the people who use it and the data involved, then agree what comes first.
You doYou introduce us to the people who use the process and share any existing files.
Design
We doWe outline the screens, data and permissions, with options and trade-offs written out.
You doYou review the outline and choose between the options.
Build
We doWe build and test in short releases, so you can use real screens early.
You doYou try each release and tell us what to change.
Release
We doWe deploy to your hosting, write the handover notes and walk your team through them.
You doYou confirm the release and decide what support you want afterwards.
Quality
Quality and handover
How the work is checked, accepted and passed to you.
Tested as it is built
Automated tests run on every change, alongside review by a second engineer.
Access reviewed
Roles and permissions are checked before each release.
Code that is yours
Source code and deployment notes live in your repositories.
A defined handover
Hosting, access and documentation pass to your team with a walk-through.
Tools
Tools and technology
Tools we use in delivery. We choose them to suit your team, and the list does not imply any partnership. Logos belong to their owners.
- React
- Next.js
- Node.js
- TypeScript
- PostgreSQL
- Docker
- GitHub Actions
Engagement
Engagement and cost factors
Ways to work with us
A scoped project
A defined application, built, tested and handed over.
A team alongside yours
Our engineers work with yours, in your repositories and reviews.
Ongoing development
A steady rhythm of improvements after the first release.
What shapes scope, timing and cost
- How many user types and workflows are involved
- What data exists and has to be brought across
- Systems the app must connect to
- Security and access requirements
- Hosting and where data must be kept
- How much support you want after release
Scope and cost are confirmed with you in writing before work starts.
FAQ
Frequently asked questions
We recommend a stack from your requirements and the skills of the team who will maintain it, and explain the choice in writing.
You do. It is delivered to your repositories and runs in your own hosting.
Often, yes. We start with a review of the existing code and confirm what can be extended and what should be reworked.
Yes. We usually suggest releasing the most important workflow first and adding to it once people are using it.
Build the application your process needs. Start with a conversation.
Tell us what you want to build and we will come back with next steps.
Talk to usRelated