Valley of Dev
204-510-2068Get a quote
Valley of Dev

Six samples, and none of them are clients.

We’re not going to dress up pretend jobs as real ones. These are concepts for made-up Winnipeg businesses, built to show how we’d think about a project like yours and what it would cost to start.

Get a quote

These are illustrative concepts. The businesses are fictional. Any phone numbers use the 555-01xx range and any domains end in .example.

The six samples, on shelves

Sample concept, not a client project

A plumber’s website that takes booking requests

Kettleby’s old site is one long page with a phone number. After hours, nobody can ask for a visit, and the owner can’t change the service list without calling someone.

What it shows: How a small service business gets a site that works at 9 p.m., without turning into an online scheduling system it didn’t ask for.

kettleby-plumbing.example

Sample concept, not a client project

This sample does not handle real patient data. It’s a concept only, with no health-data compliance claims.

Intake forms and documents for a physio clinic

New patients fill in paper forms in the waiting room, and referral letters arrive by fax and email. Front-desk staff retype it all.

What it shows: How we’d scope a web app: one clear job, a short list of user roles, and a firm line between version one and later ideas.

wexcombe-physio.example

Sample concept, not a client project

One sale, three places updated

Orders come in through the online shop. Someone copies each one into the accounting software and then into the stock spreadsheet. On busy weeks the spreadsheet is wrong by Wednesday.

What it shows: That “automation” is mostly careful rules and good error messages. The clever part is deciding what happens when the data is messy.

ladlow-baking.example

Sample concept, not a client project

A deli’s online store, for pickup and local delivery

The deli sells smoked fish, house sausage and a shelf of imported pantry goods. Customers phone in orders, and the owner takes them on a notepad between customers.

What it shows: That a small shop with a real catalogue can sell online without a big platform, and what outside costs to expect on top of the build.

ostrander-market.example

Sample concept, not a client project

Job notes and photos from the truck

Crews text photos to the office and write notes on whatever’s in the truck. By the time the invoice goes out, nobody’s sure which driveway the photo belonged to.

What it shows: What an MVP is: one core job done properly, with a written list of what’s left for version two.

crewslate.example

Sample concept, not a client projectIllustrative scenario

This is an illustrative scenario. It describes how a rescue like this could go. We’re not claiming we did it.

A 2012 booking site, moved somewhere safe

The developer who built it is long gone. The site is PHP from 2012, the host keeps warning about an old PHP version, and nobody has the admin login. Customers book canoes through it every summer.

What it shows: That a site nobody understands can be looked at calmly. Nothing is touched until you’ve agreed to a plan.

birchwater-canoe.example

No client names, no results, no numbers. When there’s real work we’re allowed to show, it’ll go here, labelled as real.

The samples in full

Sample concept, not a client project

What we’d consider

  • Whether “request a visit” is enough, or the shop really needs live booking (often it isn’t, and live booking adds cost).
  • Emergency wording: what the page says when someone has water on the floor, and a phone number that’s visible without scrolling.
  • Who updates service pages and seasonal notices, and what they’d need to learn to do it.
  • Which towns and neighbourhoods the shop actually serves, so the service-area page doesn’t overpromise.
  • Photos: real shop photos, or none. We’d rather ship with none than with stock plumbers.

A plumber’s website that takes booking requests

Fictional business Kettleby Plumbing & Heating kettleby-plumbing.example 204-555-0142

The problem

Kettleby’s old site is one long page with a phone number. After hours, nobody can ask for a visit, and the owner can’t change the service list without calling someone.

What we’d build

A business website of about eight pages. A page for each main service (drain clearing, water heaters, furnace tune-ups), a service-area page, and a booking request form that emails the shop. The owner edits text and prices in an editor they can use themselves.

What it demonstrates

How a small service business gets a site that works at 9 p.m., without turning into an online scheduling system it didn’t ask for.

Starting price from $3,9005 to 10 pages, editable.

Business websites, from $3,900

Sample concept, not a client project

This sample does not handle real patient data. It’s a concept only, with no health-data compliance claims.

What we’d consider

  • What health-privacy rules apply to a real clinic, and who confirms that. For a real project that’s the clinic’s own advisor, and it would shape hosting and storage choices before we wrote any code.
  • Who can see what: front desk, practitioners, patients.
  • What happens to a form someone starts and abandons.
  • Whether the clinic’s existing booking software stays, and whether it has anything we’d need to connect to.
  • Accessibility for patients who are in pain, older, or using a phone one-handed. Big targets, short steps, no timeouts that wipe a half-finished form.

Intake forms and documents for a physio clinic

Fictional business Wexcombe Physio wexcombe-physio.example 204-555-0117

The problem

New patients fill in paper forms in the waiting room, and referral letters arrive by fax and email. Front-desk staff retype it all.

What we’d build

A web portal. A new patient gets a link, fills in an intake form from home, and uploads a referral letter. Staff see a simple list of who has finished and who hasn’t, and download what they need.

What it demonstrates

How we’d scope a web app: one clear job, a short list of user roles, and a firm line between version one and later ideas.

Starting price from $9,500

Web apps and portals, from $9,500

Sample concept, not a client project

What we’d consider

  • Which system is the source of truth for stock: the shop, the spreadsheet, or the accounting package.
  • Returns, partial refunds and bundles (a “cake kit” that is really four products).
  • What happens when a product is renamed in one place but not the others.
  • API limits and changes on the vendors’ side, which is a real reason to have a care plan.
  • Admin access: we’d ask for the narrowest access that gets the job done, and only for the length of the work.

One sale, three places updated

Fictional business Ladlow Baking Supply ladlow-baking.example

The problem

Orders come in through the online shop. Someone copies each one into the accounting software and then into the stock spreadsheet. On busy weeks the spreadsheet is wrong by Wednesday.

What we’d build

An integration. When an order lands in the Shopify store, the sale is recorded in accounting and the stock count in the spreadsheet drops by the right amount. If something doesn’t match, a short email tells the owner what and why.

What it demonstrates

That “automation” is mostly careful rules and good error messages. The clever part is deciding what happens when the data is messy.

Starting price from $2,200

Integrations and automation, from $2,200

Sample concept, not a client project

What we’d consider

  • Shopify or WooCommerce. We’d lay out the trade-offs, and our store page has a side-by-side.
  • Perishables: order cut-offs, pickup windows, and how to say “not today” clearly.
  • Platform subscription and payment processor fees. They’re ongoing costs paid by the shop, not part of our build price.
  • Tax settings. We’d set them up the way you tell us to, and your accountant decides what applies.
  • Who photographs the products, and how many photos is realistic.

A deli’s online store, for pickup and local delivery

Fictional business Ostrander Deli & Market ostrander-market.example 204-555-0163

The problem

The deli sells smoked fish, house sausage and a shelf of imported pantry goods. Customers phone in orders, and the owner takes them on a notepad between customers.

What we’d build

An online store on WooCommerce. A catalogue of about two hundred products, pickup time slots, and a simple local delivery option. The owner adds and hides products in a couple of taps, so “sold out” can be done between customers.

What it demonstrates

That a small shop with a real catalogue can sell online without a big platform, and what outside costs to expect on top of the build.

Starting price from $6,500

Online stores, from $6,500

Sample concept, not a client project

What we’d consider

  • Winter reality. Gloves, bright snow glare, one-handed use, and a weak signal in a back lane.
  • Offline first: notes and photos saved on the phone and sent when there’s signal.
  • Which accounts the app lives under in the Apple and Google stores: yours, never ours.
  • Photo storage costs, which grow with use.
  • What’s out of version one, such as scheduling, quoting and GPS tracking, written down so nobody is surprised.

Job notes and photos from the truck

Fictional business Ridgemoor Landscaping & Snow crewslate.example

The problem

Crews text photos to the office and write notes on whatever’s in the truck. By the time the invoice goes out, nobody’s sure which driveway the photo belonged to.

What we’d build

A cross-platform mobile app for iPhone and Android. A crew lead opens a job, snaps photos, types or dictates a note, and it all files itself under that address. The office sees it in a plain web list.

What it demonstrates

What an MVP is: one core job done properly, with a written list of what’s left for version two.

Starting price from $18,000

Mobile apps and MVPs, from $18,000

Sample concept, not a client projectIllustrative scenario

This is an illustrative scenario. It describes how a rescue like this could go. We’re not claiming we did it.

What we’d consider

  • Do you still control the domain and the hosting account? That decides how quickly anything can move.
  • Where the bookings live. In a database, an inbox, or a spreadsheet nobody mentions.
  • Which URLs people have bookmarked or Google knows about, so a move doesn’t strand them.
  • Passwords. We’d ask you to change any you shared with us once the work is done.

A 2012 booking site, moved somewhere safe

Fictional business Birchwater Canoe Hire birchwater-canoe.example

The problem

The developer who built it is long gone. The site is PHP from 2012, the host keeps warning about an old PHP version, and nobody has the admin login. Customers book canoes through it every summer.

What we’d build

We’d start with the $1,200 audit: a written report on what’s there, what’s risky and what the options are. Then probably one of three paths. Patch it, move it to a current stack with the same booking flow, or rebuild it. The owner picks.

What it demonstrates

That a site nobody understands can be looked at calmly. Nothing is touched until you’ve agreed to a plan.

Starting price $1,200 flatFixes are quoted from the audit.

Fix or take over a site, audit $1,200 flat

Got a job that looks like one of these?

Tell us what you’ve got. The form has a spot for your current site or files, and it doesn’t take long.

Get a quoteor call 204-510-2068

The businesses in our samples are fictional. Prices in CAD, before applicable taxes.

CallGet a quoteGet a quote

Your quote tray

Nothing in the tray yet. Tap a tool to put it in. Tap a tag to read about it.

Starting prices. The quote gives the real number.