Excel to web app
Excel to web app conversion in Melbourne
We turn Excel and Access database workflows into proper multi-user web apps for Melbourne firms whose spreadsheet grew into a business-critical tool. Pricing schedules, matter trackers, adviser commission sheets. The shape is familiar: one workbook everybody shares, six divergent copies, formulas nobody can read, a macro that broke last month.
A real data model gives you one source of truth, the controls the spreadsheet never had, and a workflow that runs on a phone as well as a laptop.
Signs you've outgrown the spreadsheet
Excel, Google Sheets and Access all work well for a while. The signal that they no longer fit is usually operational, not technical.
- Multiple users overwriting each other. Two people open the workbook at once, one saves last, the other loses a morning's data entry. Google Sheets softens this with live co-editing, but as soon as the work needs approvals, roles or structured records, you hit the same wall from a different angle.
- Formulas nobody understands any more. The person who built the BAS workpaper template, or the WIP tracker, or the adviser commission sheet left years ago. The nested IF statements still run, and nobody wants to touch them. Every new rule gets bolted on next to the old ones until nobody can read the logic any more.
- VLOOKUP chains, macros and VBA breakage. The workbook depends on a VBA macro, an external data connection and a VLOOKUP chain three sheets deep. Something breaks every time Office updates, and the fix is a long morning for whoever inherits it.
- It cannot run on a phone. Field staff, advisers on the road or partners working from a client site cannot realistically use an Excel workbook on a phone. The workaround is an email with an attachment, and the attachment becomes a new source of drift.
- The one file that cannot be lost. There is a named workbook in a shared drive that, if it went missing tomorrow, would take the business days to rebuild. Backups exist in theory. Nobody has actually restored one.
- Admin work keeps growing. Reconciling copies, re-keying data between systems, chasing the right version of the template. The spreadsheet started as a time-saver and now quietly costs you a full day every week.
What we build instead
Database
A proper database
Proper keys, constraints and queries the database itself enforces, not cells that happen to contain data. Every change recorded: who changed what, when, and what the value used to be. The audit trail is a side effect of doing the data model properly, not a bolt-on. When someone asks why a quote went out at the wrong price, you have an answer in a minute, not an afternoon of spreadsheet archaeology.
Permissions
Role-based access
Partners, associates and clients see different things. Partners see the whole book, associates see their matters, advisers see their clients. No more hidden tabs or "please do not edit" notes at the top of a sheet that everyone ignores by Wednesday.
Integrations
Talks to your stack
Xero, MYOB, LEAP, Xplan, HubSpot and the rest of the tools your team already uses. The web app pulls from them where it should and pushes back where it must, so nobody re-keys the same record into three systems. Clean exports to Excel or CSV when your finance team genuinely needs to pivot.
Mobile
Designed for the phone
Advisers between meetings, partners between court appearances and accountants on-site at a client all need the app to work on a phone. We design the interfaces that way from the start. The common actions, updating a matter note, prepping a client review or approving a discount, all work from a phone without fighting the layout.
If your spreadsheet is really a CRM, clients, accounts, opportunities, activities, pipeline, start at the custom CRM development page instead.
Coming from Access rather than Excel? The work is close, with one twist: reverse-engineering the queries and VBA. The common questions below cover what changes.
How we approach it
Map the logic before we touch the data
Every formula, every rule, every "just ignore that tab" that actually matters gets listed. The spreadsheet is not the problem, the logic inside it is the asset, and we preserve the parts that earn their place. The audit usually finds two or three rules nobody realised were load-bearing.
Model the data properly
One source of truth. Proper keys, proper constraints the database enforces, proper relationships between records. The rules that used to rely on staff discipline now live in the model, so the system stops the wrong data getting in instead of cleaning it up afterwards.
Ship the first version in weeks, not months
We build the core workflow first. Quoting, or matter intake, or client review prep, whichever is hurting most. You use it while we port the rest. Feedback from real usage shapes what we build next, not a specification written in month one.
Port only what is actively used
Half the tabs in a mature spreadsheet are unused. We rebuild the 30 per cent that moves the business and retire the rest. The old workbook stays available read-only during the transition, so nothing you actually need is gone.
We have done this since 2007. See who we are.
When Excel is still the right answer
Web apps are not always the upgrade. Excel still wins if the use case genuinely fits it.
- One person uses it. If the workbook has a single owner who does not need to share it live, Excel is fine. The multi-user problem is the main driver for a web app, and it does not apply here.
- Infrequent monthly reconciliations. A spreadsheet that runs once a month, reads from a few sources and produces a report can sit in Excel indefinitely. Rebuilding it as a web app is more work than the saving justifies.
- Truly ad-hoc analysis. Exploratory modelling, scenario planning, the sort of work where the shape of the answer is not known at the start, belongs in Excel. Nothing beats a spreadsheet for that.
- Working discipline already in place. One canonical workbook, a sensible backup cadence, a clear owner who checks and signs off each cycle. If the discipline is real and held for years, the tool is earning its place.
- Off-the-shelf no-code fits your shape. Airtable, Smartsheet or monday.com genuinely work when your records are generic (tasks, contacts, simple projects) and your logic is shallow. Bespoke earns its keep when the rules are specific to how your firm actually prices, quotes or bills, and those rules will not bend to someone else's template.
If none of those describe your spreadsheet, you are probably past the point where discipline wins.
Proof
A Melbourne manufacturer, 30 to 50 staff, ran quoting out of a shared pricing spreadsheet. Six sales reps each kept their own copy, with different formulas, different discount rules and drifting product codes. The ops manager had tried to standardise the template twice. Each time it forked again inside three months. Off-the-shelf quoting tools had been trialled, and none matched how the product codes and discount rules actually worked.
We mapped the pricing rules, the product codes, the discount structures and the approval paths out of the spreadsheets and into a proper data model. Then we built a database-driven quoting web app with role-based access, a full audit trail and one source of truth. Reps quote from the same engine. Management sees every quote as it goes out.
Quoting throughput went up. Exact lift is under NDA. Reps stopped working from six divergent copies, and the inconsistent-formula errors went with them.
From the quote estimation case study
The pattern repeats in accounting (pricing schedules, BAS workpapers), legal (WIP trackers, trust recons) and wealth (adviser commissions, client review sheets). The same shape turns up in trade and field service businesses running job-cost workbooks, and allied health practices running rosters and CPD logs out of a shared sheet. Different spreadsheet, same forks, same fix.
Common questions
How long does this take?
Three to four months to a first usable release for most builds. We ship the core workflow in the first few weeks. The quoting engine, the client record, the stock ledger, whichever part is hurting most. You use it while we port the rest. Nobody waits six months staring at a project plan before anything changes on the ground.
What about users who love Excel and don't want to change?
They usually have a point. Excel is fast, familiar and the formulas are visible. When we replace a spreadsheet, we keep the things people liked about it: quick data entry, inline editing, exports back to Excel for the analysis work that belongs in a spreadsheet. What goes is the version chaos, the broken VLOOKUPs and the one file that cannot be lost. The same goes for Airtable or Smartsheet. They feel Excel-ish and they handle the version chaos. Where they stop is custom logic: your pricing rules, your approval paths, your product model. If the workflow is generic, those tools land fine. If it is not, you end up building workarounds on top of someone else's schema. Most of the Excel loyalists come around once they stop merging four copies every Friday.
Can the new system stay as flexible as Excel?
For the day-to-day work, yes. We design the tables and views so admins can add fields, adjust lists and tweak reports without calling us. For the genuinely ad-hoc analysis work, we export cleanly to Excel or CSV so your finance team can still pivot and model in the tool they know. The web app owns the shared, multi-user source of truth. Excel keeps its place for exploratory analysis.
Is an Access database conversion the same work?
Close, with one twist. Access has real tables and real queries, which helps. The logic is usually hiding in the queries and the VBA, not the UI, so the first job is reverse-engineering what the database actually does. We map every query, every macro and every form event that matters, then rebuild the model on a modern database and swap the runtime for a web app. Staff keep the workflow they know, without Access breaking every time Microsoft updates the runtime.
What does it cost, roughly?
We quote each build after the fixed-price systems diagnostic. Cost depends on how much logic is buried in the spreadsheet, how many users and roles you need, what has to integrate with Xero, MYOB, LEAP or Xplan, and how much history has to come across. We do not publish ranges because those answers move the number too much. The diagnostic gives you a firm figure before you commit to the build. Worth noting on the trade-off: no-code tools like Airtable, PowerApps or AppSheet are cheaper to start but the per-seat pricing compounds, and the ceiling shows up around custom logic or 30-plus users. A bespoke build is a bigger upfront number and a smaller long-run one.
Not sure if Excel is the blocker?
Start with a conversation. We will tell you whether a web app is worth the spend, or whether a tighter Excel discipline will hold for another year.