Software and growth systems for small teams
Turn Google Sheets into a web app
Google Sheets makes collaboration easy until the sheet also becomes the interface, database and permissions system. Staff need different views, customers should only see their own records and one accidental edit can break the process. A web app can provide a controlled front door while you decide whether Sheets remains part of the backend.
Build a business application — from £6,000 for a bounded scope. Requirements and acceptance checks determine the quote.
What the finished solution should accomplish
Give a Google Sheets workflow a controlled web interface, with appropriate access, validated inputs and a clear plan for where records are stored.
What this could look like in practice
A team could keep a familiar planning sheet while staff submit structured updates through a browser form. If the workflow later needs stronger transaction handling, records can move into a database while the sheet becomes a reporting export. This staged route avoids forcing every user to adopt a completely new working method on day one.
Decisions to make before building
Check row identifiers, formulas, concurrent edits and current sharing permissions. Sheet row numbers are not durable business IDs: inserting a row must not change which customer an update targets. Decide whether changes can still be made directly in Sheets and how conflicts will be resolved. Keep credentials and access enforcement out of the browser.
When a simpler option is enough
A form connected to a sheet, a no-code interface or existing workspace features may be sufficient. Custom development is a better fit when access rules, complex validation or integrations need more control. At high write volumes or where conflicting edits are costly, consider a database rather than treating Sheets as a permanent application backend.
An initial scope could include
- Sheet structure and permission review
- Validated forms and role-specific views
- Stable record mapping and migration options
How we would check the work
- Insert and reorder rows without misdirecting updates
- Test simultaneous edits and permission boundaries
- Verify users cannot obtain backend credentials
Must we migrate all our data immediately?
No. A staged build can keep Sheets in use while introducing a safer interface. The feasibility depends on volume, data sensitivity and how much direct editing continues, so those constraints should be examined before choosing that route.
Scope, ownership and working together
You work directly with Joel from discovery through implementation. We agree the outcome, exclusions and acceptance checks before a build. You receive access to the code, deployment and handover documentation. Hosting, third-party services and ongoing support are identified separately; owning the code does not make operating costs disappear.
Build a business application — from £6,000 for a bounded scope. Requirements and acceptance checks determine the quote. Permissions, migration, source-system access and the number of workflows affect scope. Hosting, maintenance and further milestones are agreed separately. Smaller extensions to existing infrastructure can receive a smaller quote.
Related next steps
Have a problem worth solving?
Tell me what you want to change, what is blocking it and the budget you have in mind. We can establish fit and agree the next step by email.
Send a project brief