RFI-01Does Ozwebnet work outside Adelaide?
Yes. Adelaide first, Australia-wide, remotely. The same fixed-quote, milestone-staged process applies wherever in Australia you are.
Every request for information from every sheet of the set, gathered here: how a build is priced, who owns the code, how long it takes, what happens if you stop partway, and how to reach us. If your question is not here, 1300 699 321 answers it Monday to Friday, 9 am to 5 pm Adelaide time.
1300 699 321 Mon–Fri 9–5 ACST · REPLY WITHIN ONE BUSINESS DAYYes. Adelaide first, Australia-wide, remotely. The same fixed-quote, milestone-staged process applies wherever in Australia you are.
Yes. You receive the source code with the intellectual property assigned to you.
One fixed quote, set before the build and staged against milestones. Each milestone ends with a working system; stop at any milestone and keep what has been built.
No. Every website and application is written from scratch in code.
A development studio: we design and write the software; we do not sell marketing.
No. Everything is written from scratch in code.
Yes — an online store with an integration is one quote, staged against one set of milestones.
Adelaide first, Australia-wide, remote-capable.
It gives you control of what search engines read — structure, headings, speed, structured data — instead of a theme deciding. Rankings depend on content and competition; our job is that nothing in the build gets in the way.
Sometimes. Parts that change often — prices, news, staff, opening hours — get an editing screen you use yourself; pages that rarely change are kept as plain pages. Which parts get a screen is set in the quote, and the source code is yours either way.
No. Everything is written from scratch in code.
One fixed quote, set in writing after a short scoping conversation and before any build starts, staged against milestones.
Yes. Adelaide first, Australia-wide, remote-capable.
The rebuild is planned so it does not. Every old address is listed before the build starts and is either kept or redirected to its new page, so links and search results still land. Where a page ranks afterwards still depends on what it says and who else competes for the search; our part is making sure the move itself does not get in the way.
Yes. The new site is written beside the old one, which stays live and untouched. Once the new site has been checked at every old address, your domain is switched over in one move.
Yes. What the old site publishes is read and carried across page by page, and the new site is written from scratch in code with no theme, page builder or plugin stack. You keep your domain, and the old subscription can be closed once the new site is live.
One fixed quote, set in writing before the build and staged against milestones. It is set after the survey of your current site, so it covers the pages, redirects and content work your site actually needs.
Yes, Australia-wide. The survey, the build and the switch-over all happen remotely, on your domain, wherever in Australia you are.
Yes. Every branch, franchise or brand gets a page with its own address, opening hours, phone number, staff and local services, and its own LocalBusiness structured data, so search engines can list it for its own suburb or town rather than folding it into head office.
Yes, where the quote includes it. Location details live in one register; a branch can be given a screen for its own entry — hours, phone, staff — while the shared pages stay with head office. Who may change what is settled at the specification stage, and the source code is yours whichever way it is set.
Yes. The same code can carry a different logo, colour set and domain for each brand or franchise, so one build serves several fronts, and a change to shared content appears on all of them at once.
Opening one is a new entry in the register: its page, finder result and structured data appear from that entry, not from a new build. Closing one retires the page with a redirect, so old links and listings still land somewhere useful.
One fixed quote, set in writing before the build and staged against milestones. The scope depends on how many locations and brands there are and how much differs between them, which is settled at the specification stage. Source code delivered, IP assigned to you.
No. WordPress is a general-purpose CMS you install and then fit a site into. A custom CMS is written for your site, with one editing screen for each part that changes and nothing else. If your content lives in WordPress today, it comes across.
The parts that change often — prices, menus, stock, staff, news, jobs, opening hours. Anything that stays the same from one year to the next is left as a plain page with no screen behind it. The list of parts that get a screen is agreed in writing at the specification stage.
No. Each screen has plain fields — text, a picture, a price, a date — in the order you fill them in. You change a field, check the preview and publish, and a short written guide comes with each screen.
One fixed quote, set in writing before the build and staged against milestones. What sets the price is how many parts of the site need an editing screen, which is why that list is agreed first.
Yes. The source code for both the site and its editing screens is delivered with the IP assigned to you, so any developer can maintain it after us.
One fixed quote, set in writing before the build and staged against milestones. No hourly meter.
Yes — source code delivered, IP assigned to you.
It depends on scope. The fixed quote comes with a milestone schedule and its timeline, so you know how long each stage runs before you commit.
Yes. Adelaide first, Australia-wide, remote-capable.
Stop at any milestone and keep a working system.
One fixed quote, set in writing before the build and staged against milestones. The price depends on what the portal shows and which systems it draws from, and it is fixed before any build starts.
Yes. The portal draws invoices from your accounting package so the customer sees the same figure your office does, with a pay-now button through your payment provider and a receipt that reaches both of you.
A portal needs records to show. If your jobs already live in a job system, an accounting package or well-kept spreadsheets, the portal draws from them. If they live nowhere yet, we will say so — a job management system may be the right first build.
Yes — source code delivered, IP assigned to you. The portal runs on your own domain.
Yes. Adelaide first, Australia-wide, remote-capable. A portal is specified, built and launched online, so your customers' logins work the same from anywhere in Australia.
One fixed quote, set in writing before the build and staged against milestones. The scope that sets it — quoting, scheduling, the field app, invoicing, the accounting connection — is agreed at the specification stage, and you can stop at any milestone and keep a working system.
If one of them fits how you work, use it, and we will say so. A custom build is for a business whose quoting, scheduling or invoicing works differently from what those products assume, or that must connect to systems they do not. The result is yours: source code delivered, IP assigned to you.
Yes. The field screens are built for the phone or tablet in the van: the day's jobs, the site details, a checklist, photos, a signature, and the hours and materials, captured on site and synced back to the office.
Yes. Invoices, payments and customer contacts pass between the system and Xero or MYOB, so the books match the jobs without anyone typing them twice.
Yes, Australia-wide. Adelaide first, remote-capable: discovery and every milestone review can run over a call, and the field screens are tested on the phones your crews carry wherever they are.
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.
One fixed quote, set in writing before the build and staged against milestones.
Yes — that is systems integration, built into the same quote or scoped as its own project.
No. You hold the source code and the IP.
Yes. Adelaide first, Australia-wide, remote-capable.
Stop at any milestone and keep a working system.
One fixed quote, set in writing before the build and staged against milestones. Stop at any milestone and keep a working system.
Yes. Each account sees its own price list — a tier, a contract list or negotiated prices on particular lines — with quantity breaks applied as the order is built.
Yes. Your accounting or inventory system stays the master of customers, prices and stock; the portal reads them and writes each order back as a sales order or invoice.
Not always. If your trade customers all pay the same price, an order form on the existing store may serve well today, and we will say so. A portal earns its place when prices, terms and credit differ by account.
Yes, Australia-wide. Adelaide first, remote-capable. The portal is yours wherever you are: source code delivered, IP assigned to you.
Every product, category and content address on the old store is mapped to its new address and redirected, so the pages that already rank keep resolving. No ranking can be promised; what is in scope is a redirect for every old address.
Yes. The new store is built and tested on a private address against a copy of your data, and the domain is switched in one planned cutover once test orders pass.
Customer accounts and order history come across. Where the old platform will not release password hashes, returning customers set a new password on first login, and the store tells them so.
One fixed quote, set in writing before the build and staged against milestones.
Yes — source code delivered, IP assigned to you. The store is yours to change, move or hand to another developer.
One fixed quote, set in writing before the build and staged against milestones. The scope — option model, price formulas, preview, order route and job sheet — is fixed at the specification stage.
Yes. Your rates, surcharges, minimum charges and quantity breaks are built in as the configurator's own logic, and your staff change them from an admin screen without a code change.
No. A priced configuration can go to the cart and payment, or to a quote your staff approve first — for jobs that need a site check, say — whichever suits how you sell.
Yes. The source code is delivered and the IP assigned to you, so the rules, prices and drawings are yours to change or take elsewhere.
Yes. Adelaide first, Australia-wide; the survey, build and testing all work remotely.
Yes — the platform connects to the systems you run today; nothing has to be re-entered.
One reconciled copy of your figures that every report reads from, so two reports never disagree.
One fixed quote, set in writing before the build and staged against milestones.
Yes — source code delivered, IP assigned to you.
Yes. Adelaide first, Australia-wide, remote-capable.
Yes — each figure is read from the system that holds it at the moment the screen is opened, so nothing is re-entered and the dashboard is never a copy that has gone stale.
Not always. If your figures come from one system, or from systems whose numbers already agree, the dashboards read from them directly. If figures from several systems disagree, they need reconciling first — that is a data warehouse, and we will say so.
One fixed quote, set in writing before the build and staged against milestones.
Yes — source code delivered, IP assigned to you.
Yes — Adelaide first, Australia-wide. The dashboards are written in Adelaide and read from your systems wherever your office is.
Usually not. If one system holds your figures and its reports agree, dashboards can read it directly. A warehouse earns its place when two or more systems each hold a version of the same customer, job or sale and the totals disagree — and we will say so either way.
No. The warehouse only reads from your systems, on a schedule you set; nothing in the source is changed and nothing is re-entered.
One fixed quote, set in writing before the build and staged against milestones.
Yes — source code delivered, IP assigned to you. It is a standard database, so Excel, Power BI or any reporting tool can read it as well as the dashboards we build.
Yes — Adelaide first, Australia-wide. The warehouse is written in Adelaide and reads from your systems wherever your office is.
Yes. We take the spreadsheet as it is built now — every column, total and exception — record where each figure comes from, and the system produces the same report on the schedule you set, pulling from Xero, MYOB, simPRO, ServiceM8, Cin7 or your own database.
The report is held. The totals are checked against the systems they came from and against the last period; if a check fails, the person responsible is told what to fix and the report stays held until it is fixed.
One fixed quote, set in writing before the build and staged against milestones.
Yes — source code delivered, IP assigned to you.
Yes — Adelaide first, Australia-wide. The reports are written in Adelaide and run against your systems wherever your office is.
No. It connects what you keep.
Any system that exposes its data — most CRM, accounting, stock, payment and freight platforms do. We confirm each one at Survey.
Yes — this is our most remote-capable service; Australia-wide.
One fixed quote, set in writing before the build and staged against milestones.
You do — source code delivered, IP assigned.
Yes, if the system lets other software read and write its records — which simPRO, ServiceM8, Cin7, HubSpot, most online store platforms and most points of sale do, as does anything we wrote for you. Which records move, and in which direction, is listed at Survey and set in the record map before the quote.
No. Xero or MYOB stays the ledger, and your bookkeeper keeps working in it as before. What changes is that invoices, payments and contacts arrive already entered, on the account and tax codes they expect, and the month-end import goes away.
It waits. An invoice edited in both systems, a contact with two ABNs or a payment with no invoice is held in a list with the reason, for a person to decide, and nothing is written over. Every record that moved, and every one that did not, is logged as it happens.
One fixed quote, set in writing before the build and staged against milestones. It is set after Survey, so it covers the systems and record types you actually move, and the source code is delivered with the IP assigned to you at handover.
Yes, Australia-wide. The survey, the build and the cut-over can all be done remotely, and Xero and MYOB are connected to over the internet, wherever in Australia your office is.
One fixed quote, set in writing before the build and staged against milestones. Reads are built before writes, and each milestone is an API the other side can already call, so you can stop at the endpoints you need.
You do — source code delivered, IP assigned to you. Your own developers, or any other, can add endpoints later.
An integration connects software you already run, using the APIs those products expose. API development gives your own system an API, so other software — a customer's, a supplier's, your website or app — can read and write your records. Many businesses need both: the API first, then the connections that use it.
Yes. Reference documentation and a sandbox loaded with sample data are part of the typical scope, and every refused request says which field was wrong and why, so an outside developer can build and test against it on their own.
Yes — Adelaide first, Australia-wide. The API is written in Adelaide and called from wherever the other software runs.
An integration moves a record from one system to another. Workflow automation runs the whole chain of steps that record sets off — raise the invoice, email the customer, set the task — with rules that fire on their own the moment the first step happens, and stop to ask a person where a decision is needed.
If a single step between two systems is handled by Zapier, Make or a native connector for a monthly fee, keep it — we will say so. A custom rule is worth building when the chain has outgrown the tool: it needs an approval, a retry, a log you can read, or a system the tool does not connect to. The rules are then source code you own.
Where a step needs a decision, the rule stops, sends it to the right person with what they need, and carries on once they have decided. Where a step cannot finish — a system down, a record that does not match — it is tried again, then the right person is told with what to fix, and the rest of the chain waits rather than running on bad data. Every run is logged step by step.
Yes — Australia-wide. The rules connect to your systems over the internet, and the build is specified, tested and handed over the same way wherever you are.
One fixed quote, set in writing before the build and staged against milestones, priced by the number of rules and the systems each one touches. The rules are delivered as source code with the IP assigned to you.
No. These are the industries whose systems we know best and describe here; the five services apply to any Australian business that runs on software.
No. Most builds connect to what you keep — accounting, job management, point of sale, stock — so data entered once moves where it is needed.
The same way as every build: one fixed quote, set in writing before any work starts and staged against milestones.
One fixed quote, set in writing before the build and staged against milestones. The scope that sets it — a website, a job system, a customer portal, a report, an integration — is agreed at the specification stage, and you can stop at any milestone and keep a working system.
No. If it runs your jobs, keep it. The build sits beside the job system and the accounting file, not in place of them: the estimate, the hours and the supplier invoice are taken from where they are already entered and put where they are needed next, so nothing is keyed twice.
You do. The source code is delivered and the IP assigned to you at handover, so the system stays yours whoever maintains it later.
Yes. Field screens are built for the phone or tablet in the van: today's jobs, the site details, checklists, photos, a signature, hours and materials, synced back to the office.
Yes, Australia-wide. Adelaide first, remote-capable: discovery, the written specification and every milestone can run over a call, and a web application reaches your crews the same way in any state, through the browser on the phone in the van.
One fixed quote, set in writing before the build and staged against milestones. What moves it is how many screens the system has and how many of your systems it connects to — LEAP, XPM, Xero, HubSpot — not the size of the firm. Stop at any milestone and keep a working system.
No. We connect to what you keep. The practice system stays the record of the matter or engagement and the ledger stays the record of the money; the build reads from them and writes back to them, so a client is keyed once.
Yes. A client portal gives each client a login that shows their own matter or job, where it is up to, documents to sign or upload and invoices to pay, drawn from the practice system and the ledger, so the office stops fielding the same call.
You do — source code delivered, IP assigned to you. Client records stay in the systems you already run; the build reads from and writes to them, and runs on your own domain.
Yes. Adelaide first, Australia-wide, remote-capable. A portal, dashboard or integration is specified, built and launched online, and 1300 699 321 is answered Monday to Friday, 9 to 5 Adelaide time.
One fixed quote, set in writing before the build and staged against milestones. Stop at any milestone and keep a working system.
No. Your inventory or ERP system stays the master of products, stock and customers. We build the portal, the floor screens or the reports around it and connect to what you keep.
Yes. A B2B ordering portal gives each account its own price list, order history and terms, and writes every order into your inventory or ERP system as a sales order.
You do. The source code is delivered and the IP assigned to you at handover.
Yes, Australia-wide. Adelaide first, remote-capable. Call 1300 699 321, Monday to Friday, 9 am to 5 pm Adelaide time; we reply within one business day.
One fixed quote, set in writing before the build and staged against milestones. The scope that sets it — the website, the ordering page, the reports, the connections to your point of sale and your books — is agreed at the specification stage, and you can stop at any milestone and keep a working system.
No. Most builds connect to the point of sale you keep, so a sale rung up once at the counter reaches the website, the online store, the reports and the books without being typed again.
You do. The source code is delivered at handover and the IP is assigned to you, so the system stays yours whichever point of sale, roster or booking product you run beside it.
Yes. A group is one build: a website with a page per site, reports with a line per site, and a connection to the point of sale at each, under one fixed quote staged against milestones.
Yes, Australia-wide. Adelaide first, remote-capable: discovery and every milestone review can run over a call, and the system is tested against the point of sale and the devices your staff actually use.
No. Each specimen is a concept build for a fictional business, designed and coded by Ozwebnet to show the work. We do not publish client work.
Yes. A site for your business is scoped in writing and priced as one fixed quote, staged against milestones; you receive the source code with the IP assigned to you.
Because the businesses on them are fictional. The pages are here to be looked at, not to be found as if they were real firms.
Survey (discovery), Blueprint (specification), Forge (build), Temper (testing) and Deploy (launch). Each ends with a working system.
At the specification stage, in writing, before any build starts. It is staged against the five milestones.
It goes back a stage and is reworked before it moves on. The cover sheet shows one part failing at the fourth gate and going back into the fire.
Yes. Stop at any milestone and keep a working system.
Every build is priced as one fixed quote, set in writing at the specification stage after a short scoping conversation. The quote is staged against five milestones and paid milestone by milestone. There is no hourly meter.
Payment follows the milestones set out in the quote; the first payment is due at the milestone the quote names, not before the specification is agreed.
A change to the written specification is priced as a written variation before it is built. Nothing is added to the price without a variation you have agreed to.
The quote names what is included. Hosting, domains and third-party services are billed by their providers to you, in your own accounts, so nothing is tied to us.
Ozwebnet is not registered for GST, so no GST is added to a quote. If that changes, GST will be shown as a separate line.
Yes. Every milestone ends with a working system. Stop at any milestone, pay for the milestones delivered, and keep what has been built.
Yes — 1300 699 321, answered live Monday to Friday, 9 am to 5 pm Adelaide time.
We reply within one business day — by phone if you asked for a call, otherwise by email — to arrange a short scoping conversation, in person in Adelaide or remotely. The fixed quote follows in writing.
Yes, Australia-wide.
One fixed quote, set in writing before any build starts and staged against milestones.
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.