Guickie
Retail and commerce
Signed and under way
A dark store grocery business, being built from the problem statement up
Guickie is a Canadian quick-commerce startup running on a dark store model: no shopfront, small local warehouses, and groceries at the door fast. The team came to us before the app, the website, or the inventory system existed, and while the problem statement itself was still being sharpened. We are building all of it with them, alongside the groundwork the business needs to hold up in front of investors.
The challenge
Quick commerce looks like a consumer app and is actually an operations business. The part a customer sees, browse, order, wait fifteen minutes, is the easy half; the half that decides whether the company survives is what happens inside a dark store, where stock accuracy, picking speed, and what you choose to hold determine the margin on every basket. Guickie needed both halves built at once, by a team that was small and moving fast, and needed the underlying thinking to be legible to outside investors at the same time. That last part is what usually gets skipped: founders build the product, then try to reconstruct the reasoning for a VC months later from memory and a folder of screenshots.
What we did
We started before the build, on the problem statement, because a dark store business that has not decided precisely who it serves and how fast will build the wrong inventory system and find out expensively. We ran pain point collection with the team, put the findings into a shared business knowledge base rather than leaving them scattered across chats and calls, and worked through the market alongside them. That knowledge base is doing double duty by design: it is how the team makes decisions week to week, and it is the substance behind an investor conversation, so the reasoning is written down while it is fresh rather than reconstructed later. The platform is being built on top of that: the customer-facing website and app, and the inventory system the dark store actually runs on, treated as one system rather than a storefront with a warehouse tool bolted to it.
The result
This one is live work, not a retrospective. The contract is signed, the engagement is under way, and we are building alongside the team as they move toward raising. We would rather say that plainly than write up an outcome that has not happened yet: this page gets filled in with what actually came of it, and with the link to the product, as the milestones land.
Every piece of it, stage by stage.
- 01
Problem statement
Getting precise about who Guickie serves, in what radius, at what speed, and what it is deliberately not doing. Every downstream decision about stock, staffing, and software falls out of that, so it came before any of them.
- 02
Pain point collection
Working through where the existing options fail, for shoppers and for the people running the operation. Structured collection rather than opinion, because the difference decides what gets built first.
- 03
Business knowledge base
One place holding what the team has learned, decided, and rejected, and why. It stops the same argument being had three times, and it is the raw material an investor deck is written from rather than invented from.
- 04
Market analysis
The Canadian quick commerce landscape, what has been tried, where the economics have broken for others, and what that implies for basket size, catalogue, and delivery radius here.
- 05
Brand and domain
The name, the identity, and the domain and accounts under it. The groundwork a company needs before it has anything to sell, handled so the founders are not the ones doing it.
- 06
Website and app
The customer-facing side: browsing, ordering, and tracking, designed around a fifteen minute promise rather than a conventional grocery basket, on the web and on the phone.
- 07
Inventory system
The half that decides the margin. Stock accuracy per dark store, picking flow for the people on the floor, and the catalogue and replenishment decisions the operation lives or dies by.
- 08
Investor readiness
The fundamentals in shape for the conversations ahead: the model, the numbers, and the reasoning documented as the work happens, so a VC is reading something that was written down at the time.
- 09
Ongoing
We are in this one now, not looking back at it. The engagement continues alongside the team as the business moves toward its raise.
Scope of the engagement
- Problem statement
- Pain point collection
- Business knowledge base
- Market analysis
- Website
- Mobile app
- Inventory system
- Dark store operations
- Investor readiness
Wherever you’re starting from, let’s figure out the next step.
Tell us what you’re building. We’ll tell you honestly whether we’re the right team for it.