Service
Web app development
We build web apps for agencies and brands that need a working tool as well as a website, including calculators, quizzes, configurators, microsites, portals and SaaS products. We scope the experience, integrations, measurement and ownership together, so the delivered code keeps working after the engagement ends.
The work behind the service.
A marketing website and an application solve different problems. A site can explain an offer and capture an enquiry. An application may need accounts, stored records, calculations or an integration that changes another system. We define the real workflow before choosing complexity, so a simple content need does not become an unnecessary software project.
Ownership means more than receiving a link to the finished product. Your team needs the code, relevant accounts and the documentation to understand the deployment and integrations. We agree on those assets before building. The handover test is whether your team can continue to change the system without needing permission from us.
What's included.
- web apps and SaaS builds
- campaign microsites
- AI calculators and estimators
- configurators and interactive quizzes
- customer portals and account areas
- CRM and platform integrations
- tracking and consent setup
- documentation and handover
What a web app can do for marketing.
A web app gives people something to use, not only something to read. A calculator can show a likely cost or saving. A configurator can help someone build the right product. A quiz can recommend a next step and qualify a lead while it does.
These tools can also collect useful first-party information with clear consent, and they can give a campaign something to link to beyond another landing page. We only recommend them when they help someone make a real decision. If a clear page would do the same job, we'd build the page.
Common web apps we build.
Calculators and estimators
These turn your pricing or expertise into a quick answer. The logic gets checked with your team and tested with representative inputs before launch.
Configurators and quizzes
These guide people toward the right product or service, then pass what they chose to your sales team or CRM.
Campaign microsites
These give a campaign its own experience, with a clear end date and a plan for what happens to the site and its data afterward.
Portals and internal tools
These add accounts, stored records or connected processes. They need more planning around permissions, security and maintenance.
SaaS and first releases
We define the smallest useful release, then build it so another team can keep working on the code.
Custom build or existing tool.
You don't always need custom software. If an existing product does the job, costs less and lets you export your data, it may be the right answer. A custom build makes more sense when the workflow is specific to you, when you need to own the system, or when the tools you've tried keep getting in the way.
We compare those options before building. We also make outside services and their costs visible, so you know what you're committing to after launch.
Security and data.
Web apps often hold information that a marketing site doesn't. We agree on what gets collected, who can access it, where it's stored and how long it's kept. We also check permissions and test how forms and integrations handle unusual inputs.
How it works.
- 01
Define the user journey
We map the people using the app and the action they need to complete. Content, forms and any interactive tools are listed against that journey. We separate the first useful release from features that can wait.
- 02
Agree on architecture and ownership
We choose the build approach around the workflow, integration needs and handover requirements. Account ownership and deployment responsibilities are explicit. We document external services so their costs and limitations are visible.
- 03
Build the pages and workflows
We implement the agreed content, interactions and integrations. Forms and calculations are tested with representative inputs. The work remains readable enough for another team to maintain rather than relying on hidden configuration.
- 04
Validate measurement and search basics
We inspect headings, metadata, page links and conversion events. We test the consent paths and the important actions on different screen sizes. Where server-rendered content is required, we check the page response rather than trusting only the browser view.
- 05
Launch and hand over
We deliver the code and operating documentation under the agreed ownership arrangement. We review deployment, integrations and common support tasks with your team. Any ongoing maintenance is scoped separately so the responsibilities remain clear.
How we price it.
We bill hourly and set the scope in hours. Strategy and advisory are CAD $175/h. Media management and execution are CAD $110/h. We separate those kinds of work in the estimate so you can see what is being bought, rather than hiding them inside a percentage of spend.
We agree on the deliverables, dependencies and review points before starting. If new work appears, we discuss the hours before expanding the scope. Engineering builds, hosting, software subscriptions, creative production and advertising budgets are identified separately where relevant. We confirm the applicable engineering rate in the scope rather than assigning a media rate to a technical build.
You can engage one discipline without buying the others. A tracking correction does not require ongoing media work, and a media engagement does not require a website rebuild. We recommend a sequence only when the evidence shows a dependency. The estimate makes that relationship visible, so your team can decide what to do now and what can wait.
We also agree on how progress will be reviewed and how hours will be reported. Your team should be able to connect the time used to the work delivered. When an access issue or an approval blocks delivery, we explain the dependency rather than letting it disappear inside an open-ended engagement.
Questions before we start.
How much does it cost to build a web app?
It depends on the features, integrations and how much needs to be built for the first release. A calculator is a much smaller job than a product with accounts and stored records. We'll give you a scope after defining the first release.
Can you connect a web app to our CRM?
Usually, yes, provided the CRM allows it. We check the connection early and test that the right information arrives in the right place.
Can you add AI features?
Yes, when they fit the job, such as an estimator or a guided recommendation. We set clear limits, test for wrong answers and make any ongoing AI costs visible.
What happens to a microsite after the campaign ends?
We agree on that before launch. It can stay live, redirect to another page or be retired, and you'll know what happens to its data.
Will we own the code?
Yes, ownership and handover are part of the agreed scope. We identify the code, accounts and documentation your team will receive. External products can have their own licences, which we make visible before committing to them.
Is SEO and tracking included?
Technical search basics and a defined tracking foundation are included in the build scope. We agree on events, tools and consent requirements before implementation. A build does not guarantee rankings or replace a separate content strategy.
How long does a build take?
Timing depends on content readiness, page count and integration complexity. We estimate after defining the first release and its dependencies.
Related services.
Notes from the work.
The case for owning your marketing tech
Rented funnels, locked-in page builders, and no-code sprawl all charge the same tax: you cannot change the thing that matters most.
Fix tracking before you raise the budget
Every account we audit that plateaued at scale had the same root cause. The platform was optimizing toward a number nobody trusted.
Start a conversation.
Tell us what you are trying to move. We will tell you which disciplines are worth engaging, and which are not.