· web design · 11 min read
How to Choose a Web Design Partner in Perth
Most Perth businesses can't tell a duct-tape web agency from a real engineering firm until something breaks. Here are the warning signs to watch for, and the green lights that mean you have found a partner worth keeping.

Perth has no shortage of web design agencies. Search “web design Perth” and you will scroll through pages of them, most promising results, affordable packages, and a team that treats you like family. A lot of them do good work. A lot of them do work that looks fine on launch day and starts falling apart the moment your business grows.
We see the second kind constantly. A client comes to us with a website or app that was built cheaply, looked great in the mockups, and now cannot do the one thing they need it to do. Connect to their booking system. Handle more than a handful of orders at once. Survive a plugin update without the homepage going blank. By the time they call us, they are paying twice: once for the build that failed, and again for the rebuild.
This post is about how to avoid being that client. The hard part is that the difference between a duct-tape agency and a real engineering firm is mostly invisible during the sales pitch. Both can show you a nice portfolio. Both can talk about SEO and mobile-friendly design. The difference shows up in the questions they ask, the documents they produce, and what happens after the invoice is paid.
Here is how to read the signs before you sign anything.
What a duct-tape build looks like
A duct-tape agency builds your website the way you would patch a leaking pipe with tape. It holds, for a while, under the right conditions. The work is usually a stock template with a stack of plugins bolted on to cover the gaps. It might look indistinguishable from a custom build on the surface. Underneath there is no real structure, no documentation, and no thought given to what your business needs the site to do beyond looking presentable.
That approach is fine for some businesses. If you need a simple brochure site and nothing more, a template and a few plugins will do the job at a price that makes sense. The trouble starts when a duct-tape agency sells that approach to a business that needs more than that, a business with stock to sell, bookings to manage, customer data to protect, or systems that need to talk to each other. The tape holds until it doesn’t, and it usually lets go at the worst possible time.
A real engineering firm treats your website or application as a system. Before anyone designs a screen, they want to understand how your business works, what the software has to do, and how it will hold up when you have ten times the traffic or twice the staff. They write things down. They test. They plan for the day something breaks, because something always does.
Software developers in Perth WA who work this way are not hard to find, but you have to know what you are looking at. Here are the signals.
The red flags
They quote a price before they understand the work
This is the clearest warning sign. If an agency gives you a fixed price in the first conversation, before they have asked a single question about how your business operates, they are quoting a template they have built ten times before, not your business.
A proper quote follows understanding. We cannot tell you what your project costs until we know what it has to do, what it connects to, and where the hard parts are. An agency that skips that step is either guessing or selling you something off the shelf and hoping it fits.
They never ask about your business logic
Pay attention to the questions an agency asks in your first few meetings. A duct-tape shop asks about colours, fonts, how many pages you want, and which competitors’ sites you like. All surface. None of it touches how your business runs.
An engineering firm asks the uncomfortable questions. How do your orders get fulfilled? What happens when stock runs out? Who needs to log in, and what should each of them be able to see? How do you handle a refund? Those questions are the agency working out what it is building, because the answers shape the whole system. An agency that does not ask them will find out the hard way, halfway through your project, on your budget.
You don’t get to own your own website
Some agencies keep your domain, your hosting, and your code under their own accounts. You pay them, but you cannot leave them, because leaving means losing everything. We have met Perth business owners who could not move their own website to a new provider because the previous agency held the keys and would not hand them over.
Your domain, your content, and your code are your business assets. You should own all of them from day one, with full access in writing. If an agency is cagey about ownership, or sets things up so you are locked in, it is telling you it plans to keep your business by holding your website hostage.
Changes go straight to your live site
Ask a simple question: where do you test changes before they go live? If the answer is a shrug, or “we just update the live site,” walk away. That is someone editing your business in production, with no safety net and no way to undo a mistake.
Real development teams use version control, so every change is tracked and reversible. They test before they ship. They keep a staging environment, a copy of your site where work happens safely before it touches anything your customers see. None of this is exotic. It is the baseline of professional development, and an agency that skips it is quietly handing you the risk.
The whole build rests on one person
Plenty of capable freelancers build good websites. The risk is concentration. If one person holds all the knowledge, writes all the code, and keeps everything in their head, your business is exposed the moment that person gets sick, gets busy with another client, or moves on. There is no documentation to hand to anyone else, because the documentation was never written.
Ask what happens if the person you are dealing with disappears tomorrow. A real firm has a process and records that let someone else pick up the work. A duct-tape operation has a single point of failure, and that point is not on your payroll.
They have no answer for what happens after launch
Launch day is the start, not the finish. Software needs maintenance. Plugins and frameworks get security updates. Browsers change. Your business changes. An agency that treats the project as done the moment the site goes live has not thought about the part of the relationship that matters most.
A website without maintenance gets slower and less secure over time, and an unpatched site is a real risk now that automated bots scan the web constantly for known holes. If an agency has no maintenance plan, no support arrangement, and no interest in talking about month two, they are selling you a launch, not a working system.
The green lights
They demand a requirements document
This is the single strongest signal that you are dealing with engineers rather than decorators. Before writing any code, a serious firm produces a requirements document, sometimes called a scope or a software requirements specification, that sets out what is being built, why, and how it should behave.
A good requirements document captures your business goals in measurable terms, lists what the software has to do and what it explicitly will not do, identifies the parts that are technically risky, and lays out a roadmap with real milestones. It is the thing you both point at when a question comes up later. It is also your protection. Most software projects do not fail because of bad coding. They fail because nobody agreed on what was being built in the first place. McKinsey’s study of large IT projects found they run, on average, 45% over budget while delivering 56% less value than forecast, and the root cause is almost always misalignment, not engineering. A requirements document is how that misalignment gets caught before it costs you anything.
When an agency pushes to write things down before it builds, that is the most valuable work in the whole project, and it happens before you have spent anything on code.
They ask about your business before your brand
The good firms want to understand how you make money. They ask about your customers, your operations, the bottlenecks that frustrate you, and the systems you already run, your accounting software, your inventory, your CRM. They ask because a website or app that ignores how your business works is just an expensive brochure.
This is the inverse of the red flag above. Where a duct-tape agency starts with what the site should look like, an engineering firm starts with what it needs to do, then makes it look good as well. Both matter. The order tells you which kind of firm you are talking to.
They explain trade-offs instead of saying yes to everything
Be wary of an agency that nods along with every idea you float. Real engineers will tell you when something you want is expensive, risky, or a worse option than an alternative you had not considered. They will explain why a custom build makes sense for one part of your project and why an off-the-shelf tool is the smarter choice for another. That kind of honest pushback is a sign of expertise, and of a firm thinking about your outcome rather than the size of the invoice. You are paying for judgement. Agreement is easy, and it is worth very little.
They hand you the keys
A firm that builds things properly has no reason to lock you in, so they don’t. Your domain, hosting, code, and accounts are yours, documented and accessible. If you decided to take your project to another developer tomorrow, you could, with everything you need to do it.
This sounds like a small contractual detail. It is a statement of confidence. An agency that hands you full ownership is betting that you will stay because the work is good, not because you are trapped.
They plan beyond launch day
Good firms talk about what happens after launch before you have to ask. They have a maintenance and support arrangement, they monitor for problems, and they plan for your site or app to grow as your business does. If you have your own internal team for ongoing work, a good partner documents everything so your people can take over cleanly, rather than leaving you dependent on them.
The question to listen for is some version of “what does this need to do in two years?” An agency asking that is building you something with a future. An agency that only talks about launch day is building you something you will be replacing.
What to ask in your first meeting
You do not need to be technical to tell these agencies apart. You just need to ask a few direct questions and listen carefully to the answers.
Ask how they will scope the work before quoting, and whether you will get a written requirements document. Ask who owns the domain, hosting, and code once the job is done. Find out where they test changes before those changes go live. Ask what their support arrangement looks like after launch, and what happens to your project if the person you are speaking to leaves.
The answers will sort the field quickly. A duct-tape agency gets vague, changes the subject, or reassures you that none of it will be a problem. An engineering firm answers plainly, because they have answered all of it before, on every project they have run.
At WebArt Design, this is how we approach web design and software development for businesses across Perth and the wider WA market. We scope before we quote, we write the requirements down, we build with the discipline that lets software survive contact with the real world, and we hand our clients full ownership of what we build. If you are weighing up a web or software project and you are not sure whether the agency in front of you is the real thing, the signs above will tell you most of what you need to know.


