Step 1/2
project details

Tell us about
the project

Tell us everything! Share your thoughts, ideas, and any specifics about your project. The more details, the better.

Select services
selection
Clear selection
Contact Details

How can we reach you?

Final step! Fill out your contact info, and we’ll be in touch to discuss your project soon.

Dropdown
Thank you for contacting us!

We will be in touch within 48 working hours

Keep your eyes peeled for an email from one of our founders.

Okay, got it!
Oops! Something went wrong while submitting the form.

Last Updated: November 17, 2026

How to choose a web development company for your SaaS

The six things to look for, and what a good answer and a red flag sound like against each.

How to choose a web development company for your SaaS
Author
Te Manihera Woods

By Te Manihera Woods

November 6, 2026

November 17, 2026

Te Manihera is a Full Stack Developer at What IF Web, building web apps, portals and integrations in React, TypeScript, Next.js and Strapi. He worked on Carepatron's site migration.

Table of contents

A SaaS business has two distinct digital environments: its marketing website and its product. The marketing website attracts potential customers, communicates the value proposition and encourages signups. The product is where customers log in, manage their accounts and use the platform's features.

While these environments serve different purposes, they need to work together. The marketing website should provide a clear path from discovering the business to becoming a customer, while maintaining a consistent brand experience with the product.

Criterion What good looks like What to watch for
Marketing and product capability Understands how the marketing website connects with the SaaS product and the wider customer journey Treats the marketing website and product as completely unrelated
SaaS funnel experience Understands how visitors move from discovery to signup, trial and activation Portfolio full of brochure sites with no metrics attached
Shippable CMS Marketing lead can publish a new page and update content independently Email us when you need a change
Tech stack fit Recommends technologies based on project requirements, integrations and long-term goals Pushes a preferred platform without considering the projects needs
Growth measurement Tracks meaningful outcomes such as signups, conversions and organic growth "A beautiful site you'll be proud of"
NZ working hours Has clear communication processes, response expectations and ongoing support arrangements Vague promises about availability and post-launch support

Can they handle both the marketing site and the product?

A web development company doesn't necessarily need to build both. However, it should understand how they connect, where its responsibilities begin and end, and how decisions made on the marketing website can affect the wider customer experience.

A good development partner understands that the marketing website and product have different requirements, technologies and audiences. They'll know when something falls within their expertise and when collaboration with your existing product team is needed.

At What IF Web, Carepatron is a good example of working across different digital environments. We originally developed its marketing website in Webflow before migrating it to an Astro frontend with Strapi CMS. This gave Carepatron a more tailored technical foundation while maintaining the flexibility needed to manage and publish website content. The project demonstrates how technology choices can evolve as a SaaS business grows and its requirements change

Do they have SaaS experience, or just websites?

The agency's portfolio tells you a lot about the kind of work they're used to doing. If every case study is a brochure site for a trades business, they may not have considered the different requirements that come with building websites for SaaS businesses.

SaaS marketing websites have different priorities. They need to communicate complex products clearly, build trust with potential customers and guide visitors towards actions such as booking a demo, starting a free trial or signing up.

A good answer sounds like: "Here's a SaaS business we've worked with. Here's what we were responsible for, the challenges we helped solve and the results of the project." Look for examples that demonstrate an understanding of SaaS audiences, conversion goals and the technical requirements that come with marketing a software product.

It's also worth asking about the integrations they've worked with. Depending on the business, this might include HubSpot or Stripe, Intercom or Segment, and other tools that connect the marketing website with the wider business.

Ask the agency what a SaaS marketing website needs that a regular website doesn't. A good answer should cover things like a pricing page the marketing team can experiment with, a clear path from the website to product signup, analytics that help track the customer journey and a CMS that supports regular content publishing.

These details help show whether the agency understands the role a marketing website plays in a SaaS business, rather than simply approaching it as another website build.

Can the marketing team ship from the CMS without a developer?

SaaS marketing moves quickly. A feature launch one week, a competitor response the next, a conference or a new campaign. Each can require changes to the website, new landing pages or updated content. If every change has to go through a developer, the marketing team loses the flexibility to respond when it matters.

A good answer sounds like: "The CMS is built around the components your team uses most. Your marketing lead can create new landing pages using existing blocks, update content and publish changes without needing a developer for every adjustment."

A well-structured CMS gives marketing teams the freedom to make changes while keeping the website consistent with the brand and its design system. The right setup depends on the technology being used, but the goal is the same: make everyday website management straightforward without compromising quality.

The handover is just as important as the CMS itself. Training should give the people managing the website the confidence to create pages, update content and make the most of the tools available to them. This might include a live training session, recorded walkthroughs and supporting documentation.

Ultimately, a good development partner builds a website your team can confidently manage after launch, rather than making themselves necessary for every small update.

Does the tech stack fit how your product is put together?

A SaaS business may already have an established technology stack, development team and infrastructure. When choosing a web development company, it's important that they understand the existing setup before recommending an approach.

However, the marketing website doesn't necessarily need to use the same technologies as the product. In many cases, using different technologies makes more sense. What matters is choosing the right tools for the job, taking into account functionality, integrations, performance, scalability and ongoing maintenance.

A good answer sounds like: "Let's understand your existing setup and what you're trying to achieve. We'll recommend the technology that best suits the project, considering your current infrastructure, integrations and future requirements."

A capable development partner should also be able to explain why they've recommended a particular platform, what its limitations are and how it will support your business as it grows.

At What IF Web, the technologies we use depend on the requirements of each project. We've worked with Webflow, Astro, Next.js, React, Vue and Strapi across different projects. For Carepatron, we originally developed the marketing website in Webflow before migrating it to Astro with Strapi CMS.

What counts isn't whether an agency uses the same tools as your product team. It's whether they can make informed technology decisions that suit the project and provide a solution your business can maintain and grow with.

Do they measure growth, or do they measure pageviews?

A website launch is only the beginning. To understand whether a website is delivering value, you need to know what success looks like before development starts and how you'll measure it afterwards.

For a SaaS business, that might include website traffic, demo requests, free trial signups, conversion rates or the number of visitors progressing towards becoming customers. The metrics that matter will depend on your business model and what the website is designed to achieve.

A good answer sounds like: "We'll establish a set of measurable goals before the project begins. We'll identify your existing performance, decide which metrics matter most and make sure the right analytics and reporting are in place before launch. We'll then review performance over time and identify opportunities for improvement."

This might involve GA4, conversion tracking and a reporting dashboard that gives your team visibility into how the website is performing. The important thing is having clear benchmarks to compare against, rather than relying on pageviews alone.

For Carepatron, the results included monthly sessions growing from 10,000 to 450,000 and a 20% uplift in conversion rate against the pre-launch baseline. These figures helped demonstrate the impact of the work beyond simply delivering a new website.

When evaluating an agency, ask what analytics they implement, which metrics they'll track and how they'll report on performance after launch. A good development partner should understand how to measure the success of their work and help you identify where improvements can be made.

Are they close enough to work with in practice?

A successful website project involves more than delivering the finished product. Communication, collaboration and ongoing support all play an important role in the relationship between a business and its web development partner.

You want to know who you're working with, how to get in touch and what happens when you need changes or support. Whether it's a new landing page, an integration update or an issue that needs investigating, there should be a clear process for getting things sorted.

A good answer sounds like: "You'll have a clear point of contact throughout the project. We'll establish communication expectations, keep you updated on progress and explain how ongoing support works after launch."

A good development partner should also be upfront about response times, support arrangements and what is included in the original project scope. If additional development work is needed after launch, you should understand how that work is prioritised and priced.

The relationship doesn't end when the website goes live. As your SaaS business grows, your website will likely need new landing pages, updated content, additional integrations and ongoing improvements. Having a development partner who understands your business and can support those changes makes it easier to keep moving forward.

When evaluating an agency, ask who you'll be communicating with, how support requests are handled and what happens when you need work completed after launch. The answers will give you a much better understanding of what working with them will actually look like.

About What IF Web

What IF Web is a four-person creative studio based in Christchurch, New Zealand, and a Webflow Premium Partner. Since 2022, we've worked with SaaS and B2B businesses, delivering websites and digital experiences for teams from Christchurch to California.

Our work with Carepatron, featured throughout this article, is one example of how we approach the unique challenges of SaaS website development. You can explore the full project in our case study.

The six considerations outlined in this article also shape how we approach our own projects. We believe a good development partnership should be built on clear communication, thoughtful technology decisions and a shared understanding of what success looks like.

Frequently Asked Questions

What is the difference between a website and a web application?

The quickest way to tell them apart is that a website is content you read, while a web application is software you use. The marketing website shows people what your business does and gets them to sign up. The web application is what they log into afterwards, where the dashboard and the workflows they use every day live. Most SaaS businesses need both, and the two sit on different tech stacks and move at different speeds.

Should we build custom software or use something off the shelf?

The honest answer is almost always off the shelf for as long as it fits, then custom when it stops fitting. Off the shelf gets you live in weeks rather than months, and the vendor carries the maintenance cost. Custom makes sense when the tool is a point of difference for your business. That might be a workflow no competitor runs, or data your business owns that sits awkwardly inside a third-party schema. Most SaaS businesses run on a mix of both, with the custom parts being the ones that would be most painful to hand to a competitor if the relationship ever ended.

What should I look for in a custom software company?

The top criteria for a custom software build come down to a portfolio with named clients and named outcomes, and a technical lead you can speak to directly during the pitch. Beyond that, the stack they work in should match or complement what your product already runs on, and the team should give you a clear plan for how they handle the handover when the build goes live. Ask them to name a project where something went wrong and how they fixed it. A straight answer tells you more about how they operate than any sales deck.

How much does a custom web application cost in New Zealand?

Custom web applications start higher than marketing websites and scale with complexity, because they're scoped by features and business logic rather than by pages. A simple internal tool sits well below a customer-facing platform with logins, payments and integrations. Any studio quoting an application without asking detailed questions about what it needs to do is guessing. Our pricing page gives you a starting point.

Do we need a different agency for our marketing site and our product?

Most of the time, yes, with a plan for how the two talk to each other. The marketing site and the product run on different stacks and move at different speeds, which often means different teams: a marketing-site team that iterates weekly, and a product team that ships to a release calendar. One agency can own both if they have clearly separated capabilities inside the one studio, but in practice most SaaS businesses use a specialist marketing-site agency alongside their own product engineers or a product-focused dev shop. The thing worth getting right is the handover between them. The specifics to nail down are who owns the brand system, and how changes on one side get reflected on the other.

Should a SaaS marketing site be on Webflow or custom-coded?

Webflow is the default for most SaaS marketing sites these days, with custom code reserved for the cases where it clearly justifies the extra cost. Webflow gets the marketing team shipping new pages themselves within a week of handover, which is where the time and the cost savings come in. Custom code, usually Next.js, is the stronger choice when the site needs server-rendered personalisation, or when it has to pull live product data onto marketing pages beyond what Webflow’s native integrations handle. For most early- to mid-stage SaaS businesses, Webflow with a carefully structured CMS is the right call for the first three to five years.

Still Have Questions?

Contact Us

Got a Crazy Idea? We're All Ears

Reach out, share your story, and Isaac or Tom will get back to you, usually same day. Let’s make some magic together.

Four men posing for a photo in a room with concrete walls and floor, three seated on a blue couch and one standing behind. From left to right on the couch are Jacob in a blue sweater and jeans, Te Manihera in an orange t-shirt and dark pants, and Isaac in a black t-shirt with tattoos on his right forearm wearing brown shoes. Standing behind the couch is Tom, smiling broadly in a light-patterned shirt. Each man has his name written above with an arrow pointing to him.