Six starting points — not a fixed menu.

Design

Brand-aligned, mobile-first layouts designed around the people who'll actually use the site — not a template with your logo dropped in.

• Visual identity and UI direction, or working within a brand you already have
• Wireframes and page layouts before any code is written
• Mobile-first design, since most visitors will arrive on a phone

Development

From a CMS site your team can update yourselves, to a fully custom build for something a template can't handle.

• Static and CMS-based sites (WordPress, Squarespace and similar)
• Custom front-end and back-end development for non-standard functionality
• Built to match how much ongoing maintenance you actually want to do yourself

Plugins & third-party integrations

Payments, bookings, inventory and CRM tools, connected to the systems your business already runs on.

• Payment gateways and online checkout
• Booking and appointment systems
• Inventory and CRM connections between your site and back office

ERP & CRM systems

Custom, lightweight systems for the parts of the business that still run on spreadsheets — built around how you actually work, not adapted from a generic platform built for someone else's business.

• Inventory, order and stock tracking dashboards
• Customer relationship tools — contacts, follow-ups, sales pipeline
• Basic finance and reporting connections
• Sized for a small or mid-size team, not a 200-user enterprise rollout

Cloud hosting

Set up and managed with New Zealand privacy requirements in mind, so you always know where your customer data actually sits.

• Hosting on Sydney-region or New Zealand-based cloud infrastructure
• Server and environment configuration
• Data location disclosed clearly, not buried in a policy no one reads

Ongoing support

Monitoring, backups and security updates after launch, so the site stays your business's — not a project that gets forgotten the day it goes live.

• Uptime monitoring and regular backups
• Security patches and performance checks
• A direct line to the person who built the site when something needs changing

Something else technical

The six above are the most common shapes a project takes — they're not the limit. If it's technically feasible, it's probably something we can scope and build.

• Internal tools and dashboards that don't need to be public-facing
• Workflow automation — moving data between systems without manual re-entry
• APIs and data pipelines connecting tools that don't talk to each other by default
• Not sure it fits any of these? Describe the problem, not the solution — we'll tell you what's feasible