For early-stage founders, we build the first version of your product: accounts, payments, a proper database and the screens your customers use every day. We build it on the same foundations as FairSlice, the SaaS product we run ourselves.
A 30-minute call, then a written scope and a fixed price. Nothing is billed until you agree to it.
These are the parts a product needs before it can take its first paying customer. Where a technical term helps, it is in brackets, so you can match it to what other developers tell you.
Your product's data lives in PostgreSQL, an open-source database. We design its structure at the start so it can grow without a rewrite a few months in.
Sign-up, login, password reset and permissions are in place from the first week. We use the same setup that runs our own products, so the awkward cases are already handled.
Subscriptions and plans through Stripe, and the screens your customers and your team use every day: tables, charts, settings and an admin panel.
Test and live versions of the app are kept apart, and every change is checked automatically before it reaches your customers.
| Part | What we built | Project |
|---|---|---|
| Database | PostgreSQL, with group balances that update live | FairSlice |
| Accounts | Login by phone number with a one-time code | TruBites |
| Permissions | Four staff roles, each limited to the parts of the admin its work needs | Cambay |
| Payments | Checkout with GST, UPI and card payments, and automatic renewals | TruBites |
| Releases | 22 end-to-end tests run on every change | TruBites |
| Backups | Nightly database backups, with a health check that fails when one is missed | Cambay |
| Audit trail | An append-only record of refunds, price edits and deletions, which the database refuses to change | Cambay |
| Integrations | Webhooks for nine kinds of event, signed and retried if delivery fails | FairSlice |
| Security | Rate limits, and validation of every input the server accepts | FairSlice |
| Scheduled jobs | Recurring expenses and payment reminders, run daily | FairSlice |
| AI features | Receipt scanning that reads items, tax and tip from a photo | FairSlice |
| Calculations | Federal and Ontario income tax and CPP, worked out in the browser with no sign-up | Stattraq |
You see working software every Friday.
The price is agreed in writing before the first week starts, and it only changes if the scope does.
Week 0
A call about the product, who it is for and what the first version has to do. Then a written scope and a fixed price for the smallest version that can earn money.
Weeks 1 to 10
The app runs at a real web address from the first week. Every Friday you click through a working build, and you can change direction before the work piles up.
End of the build
We set up hosting, the domain and monitoring. Two weeks of fixes after launch are included, and the code is yours once the final invoice is paid.
Monthly, cancel any month
Once people are using the product, we keep building based on what they do, billed monthly. If you bring the work in-house, we hand over the code and documents.
Five projects, each with a case study. Three are live today and one is in development.
An online shop for Indian suits, kurta sets, sarees and lehengas in Canada, with dated delivery estimates and sales tax worked out for each province.
A vegetarian meal subscription service in Ahmedabad. Customers choose a two- or three-meal plan, pay by UPI or card, and see the calories and macros of every meal.
An app for splitting shared costs such as restaurant bills, rent, trips and game nights. It reads receipts, handles over 150 currencies and turns a tangle of debts into a short list of payments to settle up.
Booking software for salons and spas, coming soon: a booking site for each salon, and one app for the front desk's calendar, deposits and walk-ins.
A free calculator that showed GTA gig drivers what they actually earned per hour after fuel, wear, insurance and tax. We ran it through 2025 and then retired it.
Why we built a free earnings calculator for gig drivers, and how it worked.
Why nearly every backend we build starts with PostgreSQL, and the extensions that let one database do several jobs.
What moves the price of a custom build, what the brackets look like, and what you should not pay for.
Web applications start at $15,000. After a call we write down the scope and a fixed price before any code is written, paid in two parts, with no hourly billing. Where the price lands depends on how many features the first version needs, which we work out together on the call.
Most first versions take 4 to 10 weeks, depending on scope. The database, logins, billing, dashboards and hosting follow the setup we already run in our own products, so most of the time goes to the features that are specific to your product.
Yes, from the day you pay the final invoice. You get the code repository on GitHub, the hosting settings, the environment variables, instructions for running it and a written summary of how the system fits together. Nothing stays locked in our accounts, and you can bring it in-house or give it to another team at any time.
Every Friday you get a working build at a real web address. You click through what was built that week, we agree what comes next, and you can change direction before the work piles up.
Often, yes. We start with a short review of the existing code and tell you in writing whether it is worth building on or whether starting again would cost less in the long run. You get that before you commit to anything.
Tell us about the product.
Send a few lines about the idea, who it is for and where it stands today. We reply within one business day, book a 30‑minute call if it makes sense, and send a written scope and a fixed price after that.
Or call 647-252-5352, Monday to Friday, 9 am to 6 pm Toronto time.
