Loading page…
What we build
Viva Studio designs and builds websites, web apps and custom software for Australian businesses, and can keep them running once they are live. This page explains what each type of build includes, how a project runs from the first call to handover, and why every job is priced as one fixed figure agreed up front rather than billed by the hour.
Projects tend to fit one of four types, and picking the right one early is what keeps a quote accurate. The boundaries are not always obvious from the outside, so here is how we draw them and what usually sits inside each.
Every engagement follows the same stages regardless of size. The difference between a small website and a large custom build is how long each stage takes, not whether it happens. You always know which stage you are in and what comes next.
Hourly billing puts the risk on you: if a task takes longer than guessed, you pay for it. A fixed price agreed after a proper scoping call puts that risk on us, which is where it belongs, because we are the ones estimating the work.
A common worry when comparing agencies is being locked in. Here is what changes hands at the end of a Viva Studio project, and what does not.
Yes. The four products below are live and were built by the studio as its own products, which is where our estimates come from: builds we have shipped ourselves, not a spreadsheet of hourly rates.
Process
Three clear steps — discover what you need, preview before we build, then launch with confidence.
We learn your goals, audience, and constraints in a free consultation. No jargon — just clarity on what success looks like.
You see wireframes and a working preview before we finalize anything. You approve the direction; we handle design, build, and technical details.
We deploy, test, and train your team. Then we stick around for support so you're never left wondering how something works.
You describe what you are trying to achieve and we ask about your customers, your current tools and your budget. There is no pitch and no obligation. Afterwards we write up what we heard as a scope with one price and a timeline, and you decide whether to go ahead.
Small adjustments inside the agreed scope are part of the job. Anything that adds new features is quoted as a separate change so you can approve or decline it. The original price does not move on its own.
No. A project can begin as a rough idea or a spreadsheet that has outgrown itself. The discovery call exists to turn that into a written scope, so all you need to bring is the problem you want solved.
Mainly decisions: feedback on the preview, sign-off at each milestone, and answers when a question comes up about how your business works. Expect short progress updates from us and the occasional question that needs a reply. You do not need to understand the technical side.
Most projects use Next.js and TypeScript for the application, Postgres (usually through Supabase) for data, and .NET where a heavier back end is needed. These are mainstream, well-documented tools, which matters because any capable developer can maintain what we hand over.