Question 1

What makes a website 'premium'?

Accepted Answer

A premium website is custom-designed, custom-coded, and built to measurable performance budgets — Lighthouse 95+ on mobile, Largest Contentful Paint under 1.5 seconds, Cumulative Layout Shift under 0.1, and Interaction-to-Next-Paint under 200 milliseconds. Those are Google's own Core Web Vitals 'good' thresholds, and most templated sites fall into the 'needs improvement' tier on mobile. The other half is craft: typographic hierarchy, motion that has a job, copy that earns its place, and a build that still looks considered six months after launch. The difference shows in the field, not the screenshot. HTTP Archive's annual Web Almanac consistently shows median mobile pages shipping around 500KB of JavaScript and 2.5MB total; our marketing builds typically ship under 160KB JS and 1.2MB total. That gap is what 'premium' means in measurable terms — not a price band.

Question 2

How much does a custom website cost in Australia in 2026?

Accepted Answer

Custom websites in Australia cost between $4,500 and $80,000 AUD ex-GST in 2026. There are four bands: local trade or single-clinic sites at $4,500–$8,000; premium marketing sites for service businesses or SaaS at $10,000–$25,000; custom Shopify storefronts at $12,000–$40,000; headless or enterprise commerce at $40,000+. GST is excluded by Australian agency convention — always confirm before comparing quotes, since the 10% adder turns a $20,000 ex-GST quote into $22,000 inc-GST. Templated alternatives (Wix, Squarespace, paid Shopify themes) cost $0–$3,000 in design fees plus $30–$300 per month in platform fees, so the gap is real. The premium pays for design judgement, performance discipline, conversion-rate work, and a stack the buyer can keep alive after handover — not for visual polish alone.

Question 3

How long does a custom website take to build in Australia?

Accepted Answer

Most custom marketing sites take 4 to 6 weeks from brief to launch. E-commerce builds run 6 to 10 weeks. Headless or enterprise commerce builds run 10 to 16 weeks. The variable isn't implementation speed — it's design judgement, content readiness, and integration count. Sites blocked on photography or copy add 2 to 4 weeks; sites with three or more third-party integrations (CRM, ERP, BNPL, inventory) add 3 to 6 weeks; migrations from WordPress or Magento with SEO redirect mapping add another 2 to 3 weeks on top. Templated builds on Wix or Squarespace can launch in days, but the constraint shifts from agency speed to platform limits — every site we have rebuilt off a templated platform was originally launched in under two weeks. The honest planning assumption: every week of timeline pressure trades against design quality, content quality, or scope.

Question 4

What's your usual process?

Accepted Answer

Our process has four phases over 4 to 12 weeks. Phase one is a 60-minute brief that ends with a fixed price and a one-page system diagram, delivered within 48 hours. Phase two is two live design directions within five working days, presented in-browser at 1440px and 390px viewports — not flat Figma frames. Phase three is a daily-Loom production build with a staging URL from day three; the client reviews section by section instead of one big reveal. Phase four is cutover: redirect mapping, analytics, Search Console submission, and 14 days of post-launch monitoring. We work async-first, so the briefing call is usually the only synchronous step. Daily-Loom replaces standups — clients spend 10–15 minutes per working day on the project rather than an hour-long weekly meeting. Marketing sites run 4–6 weeks under this cadence; e-commerce and larger systems run 8–12.

Question 5

What stack do you build on?

Accepted Answer

Our default stack is React 18 with TypeScript and Tailwind CSS, deployed on Vercel or Cloudflare Pages. React remains the most widely-used frontend framework in industry, so it is the easiest stack to hire for and hand off to a future agency. We use a headless CMS where it earns its keep — Sanity, Contentful, or Payload for marketing sites; Shopify Hydrogen for commerce. The rule for stack selection is simple: pick the simplest stack the client's team can keep alive after we leave. We avoid bespoke server frameworks, undocumented in-house tooling, and platforms that lock the code to a specific contractor. Every site we ship is hostable on a standard Node-compatible serverless platform and editable by a future agency. Where speed matters more than CMS flexibility (e.g. trade or local-business sites), we ship plain Vite with a Markdown content layer instead of a CMS.

Question 6

Do you only build websites, or also product UI?

Accepted Answer

Both. Marketing sites are the main practice, but the same craft transfers to product surfaces: onboarding flows, dashboards, settings screens, in-app empty states, and design-system components. For SaaS companies, onboarding is usually the highest-leverage design surface in the product; for marketplaces, the search and filter layer is. We pick up component-by-component or take a whole flow, depending on how the team prefers to work. We do not do native mobile development. The line for us is anything pixel-facing on the web or as a hybrid wrapper (Capacitor, Tauri); for pure native iOS or Android we hand off to one of three Australian studios we trust. Product work and marketing work go through identical phases — same brief format, same fixed-price discipline, same handover documentation. Most product engagements run 3 to 8 weeks per surface, depending on integration count.

Question 7

Where does AI automation fit in?

Accepted Answer

AI automation is our second practice, separate from web. Some clients want only a website, some want only workflow automation wired between their existing tools, and some want both — usually the site first and automation layered into the back-office afterwards. We treat them as separate engagements with a shared sensibility: the same brief format, the same fixed-price discipline, and the same handover documentation. Typical scope and pricing: lead-qualifying chat agents for service businesses ($4,500–$8,000), email triage and routing agents for inbox-heavy operators ($3,500–$6,000), document-extraction agents for accounting and admin teams ($6,000–$12,000), and end-to-end CRM automation pipelines ($12,000–$25,000). Stack: Make, n8n, OpenAI, Anthropic, and direct API integrations — no proprietary platform. AI work is async by default and most engagements complete in 2 to 6 weeks. Like the websites, the client owns every credential, prompt, and workflow after handover.

Question 8

Will I own the site after launch?

Accepted Answer

Yes — fully. After launch you own the Git repository, the design files (Figma), the analytics property, the domain registration, and any third-party accounts opened for the project (CMS, hosting, error monitoring, payment providers). We hand over documentation on launch day: a one-page deploy runbook, a one-page contributor guide, and a 10-minute Loom walkthrough. You can keep us on retainer, hire a different agency, or take it in-house. There is no proprietary platform you cannot leave, no licensed code we can revoke, and no contract clause that limits where the work can be hosted next. The reason this is worth confirming up front: many Australian agencies in the SMB tier still ship sites on proprietary site builders or licensed templates that are not portable without a rebuild. Always ask three questions before signing: Who owns the Git repo? Who owns the design files? Can we leave without a rebuild?

Question 9

How do I know it'll actually perform?

Accepted Answer

We publish performance budgets up front and hold them to launch. The floor on every marketing site we ship: Largest Contentful Paint under 1.5 seconds on mid-tier mobile, Interaction-to-Next-Paint under 200ms, Cumulative Layout Shift under 0.1, mobile Lighthouse Performance score 95+, and JavaScript shipped under 160KB gzipped. Those are tighter than Google's Core Web Vitals 'good' thresholds (LCP 2.5s, INP 200ms, CLS 0.1) because field LCP runs 30–40% slower than synthetic LCP on Australian mobile networks. INP replaced First Input Delay as the third Core Web Vital in March 2024 — any agency still quoting FID is using outdated benchmarks. You see all metrics on a staging URL before launch, and we monitor against the baseline for 14 days afterwards. Sites that miss budget at launch are rebuilt against the budget. Performance is treated as a build acceptance criterion, not a nice-to-have.

Question 10

Do you build websites for tradies in Sydney?

Accepted Answer

Yes — plumbers, electricians, builders, painters and other Sydney-based trades are a regular part of the practice. Trade sites need a different recipe than premium brand sites: tap-to-call discipline (thumb-zone primary buttons on every page), suburb pages for local search, after-hours capture (form-to-SMS for missed calls), and sub-1.5-second mobile LCP because trade buyers are mostly on mobile and on patchy networks. The Australian Bureau of Statistics' Household Use of Information Technology report has consistently shown that over 90% of Australian households now access the internet primarily on a mobile device, so the performance budget is part of the conversion strategy, not separate from it. We charge $4,500 to $8,000 AUD ex-GST for a standard trade site: 6 to 12 suburb pages, LocalBusiness + Service + FAQ schema, Google Business Profile sync, and call-tracking number setup. Treat this as a distinct vertical, not a discount template.

Question 11

What's the difference between Shopify Plus and standard Shopify?

Accepted Answer

Shopify Plus is Shopify's enterprise tier and starts at approximately USD $2,300 per month (around AUD $3,600), versus standard Shopify which runs USD $39 to $399 per month. The pricing gap pays for: custom checkout via Shopify Scripts and Shopify Functions, ten dedicated sandbox environments, a dedicated Launch Manager, higher API rate limits, multi-storefront support (up to 10 expansion stores at no extra cost), and a B2B/wholesale module. Standard Shopify covers most brands up to roughly AUD $1m in monthly revenue; Plus typically becomes worth the upgrade above that — or earlier if checkout customisation is a competitive advantage (subscription gating, complex BNPL combinations, country-specific tax logic). The conversion-rate uplift from custom checkout work is the most common upgrade trigger we see; A/B-tested checkout gains of 5–15% are common in the $1m-plus AUD revenue band. Below that threshold the upgrade rarely pays back.

Question 12

Do you work with businesses outside Sydney?

Accepted Answer

Yes. We are based in Sydney CBD but most clients are remote — recent engagements include Melbourne, Brisbane, Perth, Newcastle, Wollongong, regional NSW and Victoria, plus a handful in Auckland, Singapore and London. The work is async-first by design: the briefing call is usually the only synchronous step, and the rest moves through daily-Loom reviews, Slack or email, and a shared staging URL. Distance does not change timeline or pricing. The only difference is timezone arithmetic on launch day — Australian east-coast launches happen during AEDT business hours, and international launches are scheduled inside the client's working hours so we can monitor analytics and uptime in real time for the first two hours after cutover. We do not require any in-person meetings, though we welcome them when convenient. Melbourne is consistently the most common client location after Sydney itself.

Websites that don't look made for the internet.

A Sydney web design agency and AI automation studio for Australian businesses.

Two practices.
One sensibility.

Websites that feel like an event.

Systems that run themselves.

How we work,
end to end.

Brief

Design

Build

Ship

How we work,
end to end.

Brief

Design

Build

Ship

Built for the businesses
that care how they look.

Frequently asked,
honestly answered.

Build something worth visiting.

Websites that don't look made for the internet.

A Sydney web design agency and AI automation studio for Australian businesses.

Two practices.One sensibility.

Websites that feel like an event.

Systems that run themselves.

How we work,end to end.

Brief

Design

Build

Ship

How we work,end to end.

Brief

Design

Build

Ship

Built for the businessesthat care how they look.

Frequently asked,honestly answered.

Build something worth visiting.

Two practices.
One sensibility.

How we work,
end to end.

How we work,
end to end.

Built for the businesses
that care how they look.

Frequently asked,
honestly answered.