Should we do a project or a continuous arrangement?

Depends on whether anyone will own it afterwards. If nobody will, a project restarts the same decay curve in three years and DARWIN is the better answer.

Will our team be able to edit it?

That's a build requirement, not an afterthought. If the answer is no, the site begins diverging from the business immediately.

Do you handle accessibility?

Yes, audit and remediation against the standard that applies to your organisation. It's also built in rather than retrofitted, which costs a fraction as much.

What about our rankings during a migration?

Redirect mapping is part of the scope, one-to-one wherever a successor page exists. Losing rankings in a replatform is avoidable and usually a planning failure.

AliveCommerce / What we do / Web and revenue

Websites and web applications

Most business websites are built once, handed over, and then nobody can change the one page that matters. We build sites your team can actually edit, and we say plainly when a continuous arrangement would serve you better than another project.

EngagementDefined project, FBSC

Typical build8 to 16 weeks

You ownDomain, hosting, code, content

Talk to us about this What drives the cost

Fixed budgetAgreed before work starts. Scope flexes, the number doesn’t.

No vendor pays usNo commissions, referral fees or markup. Ever.

You own everythingCode, documentation, credentials — throughout, not at the end.

Nearly 20 years2,000+ projects for 500+ organizations, from SOHO to Fortune 1000.

What's included.

Scoped and priced up front. Exclusions written as explicitly as inclusions.

Corporate and marketing sites

Built for the business you are now, structured so it can keep matching the business you become.

Web applications, PWAs and SPAs

Where the site is really a tool — configurators, calculators, portals, booking and quoting.

Landing pages and campaign infrastructure

Built for measurement, with conversion tracking wired properly rather than added afterwards.

AODA and accessibility compliance

Audit and remediation against the standard that actually applies to you, with a deadline to hit.

Performance and technical SEO

Core Web Vitals, structured data, crawlability and AI-assistant legibility as part of the build, not a later phase.

Migration and replatforming

Off a platform you've outgrown, with redirects mapped properly so rankings survive the move.

How we approach it.

In this order, because doing them out of order is how these go wrong.

Structure before design

How the content is organised determines whether the site is still useful in three years. Visual design follows it.

Build for the editor

If your team can't change a page without calling someone, the site starts decaying the week it launches.

Instrument it properly

Analytics, conversion events and performance monitoring wired in at build, so you know whether it's working.

Hand over with documentation

Credentials, structure, how to add a page, what not to touch. And a frank conversation about who owns it afterwards.

Typical build

8 to 16 weeks

Corporate site through to web application

Accessibility audit

2 to 3 weeks

Fixed price, standalone, ranked by severity

Most common trigger

A rebuild quote

Often the third in a decade

Not sure this is what you need?

Tell us what's actually happening and we'll say which part of this applies — or that a different approach fits better, or that you don't need us yet. That last answer is more common than you'd expect.

Get a straight answer Or call 416-639-5876, weekdays 8:30–5:30 ET

What we work with.

Chosen on fit. We take no commission or referral fee from any of them.

AstroReactTailwindCloudflare PagesWordPressHeadless CMSWCAG 2.1 AASchema.orgCore Web VitalsGA4

If this shouldn't be a project.

Some of this work never really ends. When that's true, we'll say so rather than selling you a project that restarts in three years.

Continuous ownership

DARWIN

When the honest answer is that another project just restarts the decay curve. The site changes monthly instead of every three years.

See DARWIN

Applications behind it

Champion1

When the site is a frontend over business systems that also need owning.

See Champion1

Straight answers.

Start the Conversation.

No qualification questionnaire. No nurture sequence. A person reads it and replies within a business day — and tells you plainly if we're not the right fit.

01A person reads itNot a scoring model. It goes to whoever would actually do the work.

02A reply within a business dayUsually a question or two rather than a calendar link.

03A conversation, not a pitchTwenty to ninety minutes. No deck, no slides.

04Then, only if it's warrantedA scope or assessment with a price attached before any work starts.

Prefer to talk first? 416-639-5876 · [email protected]

About websites and web applications

Three fields. We'll ask the rest on the call.

Related.

Articles are matched by tag; services, capabilities and programs are curated.

Tell us what's breaking.

We'll tell you roughly what this costs, how long it takes, and whether it's worth doing at all — including when the honest answer is that you don't need us.

Start the Conversation

Knowledge and process

Applications and data

Customer and web

Browse by symptom instead

The structure

Continuous ownership

Before you commit

Start with one problem

Priority sectors

Also

Or by situation

Not sure you fit?

Reading

Most read

Proof

Nobody owns the application layer