From a Country Pie Shop to National Organisations: Why Your Size Doesn't Change Our Standards

Two questions land in our inbox regularly. Small businesses ask "are we too small for you?" Bigger organisations ask "can you handle something this size?"

The answer to both is yes, and the reason is the same: every site we build sits on the same fundamentals. Size changes the scope. It doesn't change the standard.

Who we've built for

A quick look through our recent work tells the story better than we can:

• Waipiata Pies. A bakery in rural Central Otago that needed to be found by hungry travellers.
• Seal Kayak Kaikōura. A tourism operator competing for bookings against much bigger players.
• Man Alive. A not-for-profit supporting men and boys, where trust and clarity matter more than flash.
• New Zealand Writers Guild. A national membership organisation with layered content and multiple audiences.
• Quantics. An Austrian software company selling supply chain forecasting to manufacturers worldwide. Yes, our clients aren't all in New Zealand either.

Different budgets, different audiences, different scale. All built in Webflow, all built the same way.

What changes with size

Here's what genuinely shifts as an organisation gets bigger:

• Page count. A smaller business usually needs 4 to 10 pages. A larger organisation often needs 20 or more across multiple sections.
• Content management. A simple CMS for news or projects, versus multiple collections for people, resources, events and member content.
• Decision making. One or two decision makers, versus committees, boards and sign-off rounds.
• Integrations. A contact form and maybe a booking link, versus CRM, membership systems, newsletters and job boards.
• Timeline. A few weeks, versus a few months with staged delivery.

What doesn't change

These are non-negotiable on every build, at every budget:

• Fast load times on real phones, not just in a test tool.
• A clear message. Within seconds, a visitor knows what you do and who it's for.
• Structure that search engines and AI tools can read: proper headings, schema markup, clean code.
• A site you can edit yourself. We build in Webflow so you're not paying us for every text change.
• Honest scoping. We quote per page based on complexity, so you're not paying big-organisation prices for a small-business site.

How to work out what you need

1. List your services. Each core service usually deserves its own page. That drives your page count.
2. Decide who updates the site. If content changes weekly, you need a CMS built for your team, not ours.
3. Name your must-have integrations. Booking, payments, CRM, membership. Knowing these upfront keeps the quote accurate.
4. Be honest about content. Who's writing the words? Do you have decent photos? We design and build, and we'll point you to good copywriters and photographers, but plan for those early.

Wherever you're at, start the conversation

Tell us what you're trying to achieve and we'll give you a straight answer on scope, cost and timing. No pressure, no jargon, no upsell.

‍