Mapping of the spreadsheets, forms and email approvals it replaces
Every sheet, shared form and approval thread the tool takes over, listed column by column, so nothing your staff rely on is lost in the move.
Internal tools are the staff-only screens a business runs on — approvals, registers, price lists, stock counts, the admin behind every job and invoice — built to replace the spreadsheet everyone is afraid to touch. They are for teams whose back office lives in shared files and inboxes. Ozwebnet writes them from scratch in Adelaide for businesses anywhere in Australia, priced as one fixed quote staged against milestones, and the source code is handed over with the IP assigned to you.
DETAIL OF SHEET 04 — WEB APPLICATIONS →
Internal tools are the software only your staff use: the admin screens, forms, registers and approval steps behind the customer-facing side of the business. A price list the sales team edits without a developer. An equipment register with service dates. A purchase order that moves from the yard to the manager to accounts. Most businesses already have these tools as spreadsheets, shared folders and email threads. A custom internal tool puts each on one screen with rules, a history and a login. It runs the office; a job system follows the work, a portal faces the customer.
Every sheet, shared form and approval thread the tool takes over, listed column by column, so nothing your staff rely on is lost in the move.
Price lists, equipment, suppliers, sites, staff details: each on its own screen with search, an edit history and the rule that stops a bad entry.
Purchase orders, leave, discounts, variations: a request goes to the right person, gets a decision, and the record shows who approved what and when. An approved order can be sent on to Xero or MYOB.
The forms staff fill in for the office — stock, maintenance, expenses — each landing in a queue the right team works through, instead of an inbox.
Price rises, supplier changes and end-of-month updates applied across a whole table at once, shown to you before anything is saved.
Your current data is brought in, cleaned and checked, so the tool starts with your history rather than an empty table.
Every change carries who made it and when, and any table exports back to a spreadsheet when someone needs one.
TYPICAL SCOPE FOR THIS KIND OF SYSTEM — YOUR EXACT SCOPE IS FIXED IN WRITING AT THE SPECIFICATION STAGE.
Not sure which? Ten minutes on 1300 699 321 tells you — Mon–Fri 9–5 ACST.
One fixed quote, set in writing at the specification stage (02 Blueprint) and staged against the five milestones below. Each milestone ends with a working system; stop at any milestone and keep what has been built.
SEE THE FIVE STAGES ANIMATED →We sit with the people who run the spreadsheets and watch how a request, a change or an approval actually moves through the office.
Every screen, field, rule and approval step is specified in writing; the fixed quote is set here, staged against milestones.
Built one tool at a time, the most painful spreadsheet first; each milestone ends with a working screen your staff use.
Checked against your real records and the edge cases your staff know about, and tested before launch.
The tool goes live beside the spreadsheets it replaces, and you receive the source code with the IP assigned to you.
One fixed quote, set in writing before the build and staged against milestones. Each milestone is a working tool, so you can start with the worst spreadsheet and stop there if that is all you need.
Yes — source code delivered, IP assigned to you. Your own staff or any other developer can change the screens later.
Yes. Importing the spreadsheets you run today is part of the typical scope: the data is brought in, cleaned and checked, and any table can still be exported back to a spreadsheet when someone needs one.
An internal tool is the staff-only admin: registers, approvals, request forms — the screens that run the office. A job management system follows each job from quote to invoice, and a client portal faces the customer. You can build one first and add the others later.
Yes. Adelaide first, Australia-wide; discovery, build and launch can all be done remotely.
Call, or answer a few short questions — what you run, what breaks, when you need it working — and we reply within one business day. The quote is fixed in writing before any build starts.