We design and build marketing sites, customer portals and custom web applications — Odoo-native or standalone. Fixed-fee per phase, your repository from day one, accessible and bilingual by default, and documented well enough that your next developer doesn't need us.
We're a small team, so we stay inside the work we're demonstrably good at: sites that generate pipeline, portals that remove manual work, and applications that replace a spreadsheet nobody wants to own.
Sites whose job is qualified pipeline. Built on a headless CMS your marketing team can actually publish from, with the SEO and analytics layer wired in before launch rather than after.
Self-serve access to the data your team currently emails as PDFs — orders, invoices, documents, tickets, claims. Usually the fastest operational payback we can point at.
The internal tool no vendor sells — quoting engines, scheduling, inspection workflows, compliance tracking. Built when configuration genuinely can't get you there.
These are the things that get cut first when a project runs late — and the things that determine whether the build is still maintainable in three years. They're in the fixed fee, so there's nothing to trade.
Code is pushed to your GitHub organization from the first commit, not delivered as a zip at the end. You watch the build happen and can hire anyone to continue it.
Core Web Vitals and JS payload limits run as automated checks on every pull request. A regression fails the build rather than being discovered by your users.
Contrast, keyboard paths, focus order, semantics and screen-reader labelling — with a manual audit before launch, not just an automated scan that misses most of it.
French is modelled as its own locale with its own content, not a translation layer bolted on. Components are sized for copy roughly 20% longer than English.
We choose technology you can staff in Montréal or Toronto next year. No in-house framework, no exotic dependency that makes us the only possible maintainer.
Architecture notes, runbooks, environment setup and a recorded walkthrough. Written for the developer who joins after we're gone, because that person always exists.
Each phase is fixed-fee with a named deliverable and an exit criterion. Nothing is built behind a curtain — staging is live and open to your team from the first sprint.
Requirements, user journeys, data model, integration audit, and a fixed quote with the assumptions written down.
Wireframes, then hi-fi screens in your design system. Prototyped and tested with real users before a line of production code.
Two-week sprints shipping to staging continuously. You review working software, not status decks.
Content load, redirect map, accessibility and performance audit, load test, then a rehearsed cut-over.
Thirty days hypercare included, then handover with training — or a monthly care plan if you'd rather we kept it.
We won't give a number before we understand the data model and the integrations — a quote produced from a sales call is a guess you end up paying for in change orders.
A marketing site on a headless CMS, built to publish from and to rank. Range depends on page count, content production and integrations.
A customer portal or custom application with real integration depth. Most of our work lands here — replacing manual operations with something people actually log into.
Multiple user types, multiple integrations, a migration to survive, and stakeholders across regions. Delivered as a sequence of independently useful releases.
Measured 90 days after launch against the baseline we recorded in discovery. Where a project missed its target we say so in the case study.
“The portal took four months and removed two full-time roles' worth of manual invoice emails. What I didn't expect was the handover — our own developer was shipping features to it three weeks after Noordev left.”
If your question isn't here, ask it on the call. We'll tell you when configuration would beat a custom build, even though that's the smaller invoice.
Three kinds: marketing websites where the goal is pipeline, customer and partner portals where the goal is deflecting manual work, and custom web applications that replace a spreadsheet or a tool nobody sells. We do not take on consumer social apps, marketplaces without a distribution plan, or crypto.
Marketing sites are CAD $3k to $5k depending on page count, content production and integration depth. Portals and applications run $95k to $250k. Platform builds with multiple user types and heavy integration start at $250k. Everything is fixed-fee per phase, quoted after a paid discovery, and we publish the assumptions the number depends on.
A marketing site takes 3 to 4 weeks from kickoff. A portal or application takes 4 to 7 months to first production release, with usable increments in your hands from week six onward. We ship continuously to a staging environment rather than disappearing for a quarter and returning with a reveal.
For marketing sites, Astro or Next.js with a headless CMS, or Odoo Website when the client is already on Odoo. For applications, Next.js and Postgres, or native Odoo modules when the data model already lives there. We pick the boring option that your team can hire for, not the one that is interesting to us.
Yes, and we prefer it. If you have a design system we build inside it and hand back new components as tokens and documented patterns. If you don't, we can run a brand identity engagement first, or design a lightweight system as part of the build so the site is extendable after launch.
WCAG 2.2 AA is included in every build, not an upsell — contrast, keyboard paths, focus order, screen-reader labelling and an audit before launch. Bilingual EN/FR-CA is our default: French is treated as a first-class locale with its own content model and layouts sized for roughly 20% longer copy.
Thirty days of hypercare on every project, then either a handover to your team with documentation and a training session, or a monthly care plan covering dependency updates, security patches, performance budgets and a block of change hours. We do not require the care plan to hand over the code.
You do. Code lands in your repository from day one under a licence transfer on final payment, infrastructure runs in your cloud accounts, and there is no proprietary framework you have to keep paying us to maintain. If you replace us, another team can read the repository and continue.
Tell us what has to be true at launch — the integration, the deadline, the budget, the team who inherits it. We'll tell you what's buildable inside it, and when configuration would be the better answer.