What we make
Five kinds of build.
One way of working.
A hard problem enters. Something useful leaves.
Every one of these runs the same six steps, ends with you holding the keys, and is quoted only after we have seen the job. Nothing on this page is a price.
Website
Pages that explain what you do and give people a way to get in touch.
This is you if
- People already know they want you, and need to check you are real
- Your work is better than the site that shows it
- You are explaining the same thing on the phone every week
What you get
- Every page written, not just designed — the words are the job
- Photography of your actual work, arranged so it does the selling
- A contact route that reaches you, tested end to end
- Hours, prices and copy you can change yourself, same day
- Search setup: structured data, sitemap, Search Console handover
What this is not
- A logo or brand identity — we work with what you have
- Ongoing content writing after launch
- Paid advertising or social management
- How long
- About three weeks, most of it in your inbox waiting on you.
- Built one
- CNC Signmaker — cncsignmaker.ca
E-commerce
A catalogue people can browse and buy from, or ask for a quote on.
This is you if
- You sell a fixed range and take payment online
- You quote rather than sell, and the quote starts with a photo
- Your catalogue is small enough that every product deserves a photo
What you get
- Catalogue, product pages, cart and checkout
- Payments through Stripe, on your own account
- Stock, prices and products editable by you
- Order notifications that actually arrive
- Tax and shipping rules for where you ship
What this is not
- Warehouse or inventory systems beyond stock counts
- Marketplace listings — Amazon, Etsy, eBay
- Product photography, though we will tell you what is needed
- How long
- Four to six weeks. The catalogue is usually what decides, not the code.
- Built one
- BK Junk Co. — bkjunkco.ca
Mobile app
Something that lives on a phone, with its own screens and navigation.
This is you if
- The thing only makes sense in a pocket, on site, or offline
- You need the camera, location, or notifications
- A website would work, but people will not keep visiting one
What you get
- One app, built once, running on iOS and Android
- Accounts, if it needs them
- Submission to both stores under your developer accounts
- A screen for you to see what is happening
What this is not
- The store developer accounts themselves — those stay in your name
- Ongoing store review appeals after launch
- Games, or anything leaning on 3D
- How long
- Scoped after we see the job. Store review adds one to two weeks nobody controls.
Full-stack application
A tool with accounts, data and a screen for whoever runs it.
This is you if
- Work is being tracked in a spreadsheet that three people edit
- You need accounts, permissions, and a record of who did what
- Someone is retyping the same data into a second system
What you get
- Accounts and permissions that match how your business works
- The database, and a plain-English account of what is in it
- An admin screen for whoever runs it day to day
- The integrations the job needs, named before we start
- Backups, and a written route back if something breaks
What this is not
- Migrating years of messy historical data, unless scoped separately
- Staff training beyond a handover session and written notes
- 24/7 on-call support
- How long
- Quoted after we see the job. These are the ones worth scoping slowly.
Single-page app
One screen that responds instantly, without page loads between steps.
This is you if
- People use it for a whole shift, not for two minutes
- Every page load in the middle of a task is a cost
- It is one job done repeatedly, not many pages to browse
What you get
- One screen that responds without reloading
- State that survives a refresh and a dropped connection
- Keyboard paths for the things done hundreds of times a day
- The API behind it, where it needs its own
What this is not
- Native desktop packaging
- Real-time collaboration between users, unless scoped
- How long
- Scoped after we see the job.
Six strikes.
Understand
The job, named before anything is drawn.
Design
Pages, type, and the words, settled before code.
Engineer
Data, accounts, and the path a job takes.
Build
We build it. You look it over. We test it.
Refine
Hours, photos, and copy still change after launch.
Deploy
It goes live. You get the keys.
Bring the problem.
Bring the problem, what should exist, and a look. We turn that into a brief we can both read. One working day. You talk to whoever does the build.