A useful solution starts with context.
A spreadsheet can be a useful beginning. It becomes a bottleneck when several people need different permissions, information is duplicated, and nobody trusts the latest version. I start with those operational problems before choosing a technology. An internal operations portal, a customer dashboard or a booking and records system should make daily decisions easier—not introduce another layer of administration. We define the essential workflows, the people using them and the information they need. Next.js, React, NestJS, Python and PostgreSQL or Firebase are possible building blocks; the right stack depends on the problem, hosting constraints and maintenance needs. A small, testable first release is often more useful than a long list of unvalidated features.
What I can help with
- Requirements discovery and workflow mapping
- Role-based dashboards, permissions and administration
- Database design, reporting and authorized API connections
- Testing, deployment and operational documentation
Bring the problem, not a finished specification.
Share the current situation and your priorities. We’ll identify missing information together before agreeing to build.
- A description of your current workflow and its bottlenecks
- Examples of records with private information removed
- User roles, must-have features and hosting constraints
You complete sensitive verification yourself. Never send passwords, PINs, tokens or OTPs in a message.
A clear sequence, with review built in.
- 01
Map the current process and agree a measurable acceptance checklist.
- 02
Design the data model, permissions and key screens.
- 03
Build agreed milestones with regular demonstrations.
- 04
Test realistic cases, access controls and failure paths.
- 05
Deploy, document and hand over the agreed release.
What you receive
- Agreed scope and milestone plan
- Working software for the approved features
- Basic documentation, deployment notes and handover
The final checklist is agreed in the scope. If an external decision or dependency prevents completion, the status and the next available step are made clear.
Pricing & running costs
Discovery determines the quote. Development is scoped by milestones; hosting, third-party subscriptions and optional maintenance are separate.
Before starting, we agree what is included, who pays third-party charges and what would require a revised quote. No fixed price or processing timeline is assumed.
Important limitations & privacy
Existing data may need cleanup before migration. Security, backup ownership and maintenance responsibilities are agreed before launch. I do not promise every requested feature is feasible within an initial budget.
Only necessary information is requested for the agreed task. Sharing, access and document retention are discussed before handling sensitive material. Read the privacy notes.
Before you get in touch
Can we start with an MVP?
Yes. We can choose the smallest useful workflow, define what is excluded and extend it after real users have tested it.
Will I own the accounts?
Account ownership, repository access and source-code handover are documented in the agreed scope.
Can you work with existing software?
I first review its code, access and dependencies. An audit may be needed before a reliable change estimate is possible.
See the thinking behind the work.
Read the case study, including what is established and what still needs confirmation.