Every number has a source
Market sizes are footnoted. Interview counts are real. If a figure on this site can't be traced to a case study or a public source, it doesn't go on the site.
ProductGurus does product, feasibility and competitor research for founders and operators, writes the brief when the answer is build, and owns the build until it ships. Local businesses get the same research for a location, a website or a Google listing. Eight products have gone through discovery here. Five were built. Three stopped when the evidence said they should. Every number on this site traces to one of them.
Seven-plus years across operations, product and IT services. Today I manage merchandising standards for a major Western Canadian retailer, where I own execution audits, process standards and the KPIs that come with them. Before that I was a Product Specialist at a martech SaaS company, turning feedback from 70+ publisher clients into requirements the product team could prioritize. ProductGurus is where I take a problem from first interview to a shipped product or a documented no-go.
I run the interviews, own the judgment calls, edit every deliverable, and sign the recommendation. If we tell you not to build something, I'm the one who will explain why on the call.
The studio started as a way to answer one question properly: is this worth building? The method that came out of it is short. Talk to the people who would pay. Size the market with sources you can check. Work out the unit economics. Then say build, wait, or no, in writing, with the evidence attached. Since then the same method has been used on shift scheduling for a unionized hourly workforce, an internal audit tool, a job-search extension, two marketplace concepts, and two hardware ideas.
Eight products have come out of it so far. Five are built and running, including the scheduling tool that started all this because a roster process was broken and nobody else was going to open a spec doc about it. The other three went as far as full discovery and technical design, where the evidence decided whether to keep going. In 2026 the studio opened the same research to local business owners as well: the café, clinic, and shop decisions that deserve the homework a startup would do. See the services
They cost us the occasional project. They've never cost a client one.
Market sizes are footnoted. Interview counts are real. If a figure on this site can't be traced to a case study or a public source, it doesn't go on the site.
Three of the eight products stopped after research. We'd rather lose the build work than watch you spend on something the interviews already killed.
Interview notes, findings, user stories, the site files, the analytics accounts. All of it sits in your name from day one, so leaving us is never a hostage situation.
No e-commerce stores. No paid ads. No "we can do anything." When a job needs a specialist we don't have, we'll say so on the first call and point you to one.
A findings deck you can act on without a translator. A brief a developer can quote from. A site audit ranked by what to fix first. If it needs a meeting to understand, we rewrite it.
I'm open to Product Owner and Technical Product Manager roles in Vancouver or remote across Canada, especially in operations, workforce or retail tech. I'm studying for PSPO I. Five products built, three stopped at discovery on purpose, and each one has a case study here.
We use AI tooling to move fast on transcription, synthesis, and drafting; a person runs every interview, makes every call, and signs every deliverable. When something goes out with our name on it, a person stood behind it: read it, tested it, and was willing to be wrong about it in public. That's the whole arrangement. Good tools, held accountable.