The Lab · working pages
The documents behind the stories
These pages hold the working documents: a scorecard for every product, the screens before and after, one prioritization grid, a decision log, and the template that turns a finding into a requirement.
Product scorecards
One card per product-
Immigrant Techies Alberta2024 – 2025
- Stage
- Delivered · volunteer since April 2025
- My role
- Technical Program Manager: clients, talent intake, team formation, PMs and tech leads, stakeholders, events, podcast
- Team
- 13 full software teams of immigrant professionals · 100+ onboarded
- Measure
- 13 MVPs across four cohorts
- The bet
- A full cross-functional team, formed on interviews and the project's needs, can take a founder's idea to a working MVP in one three-month cohort.
-
SettleSMARTApr 2025 –
- Stage
- Pilot, June to November 2026
- My role
- Project Associate, responsible for technical product management: requirements, testing, deployment and the product calls
- Team
- A full research team and a software development team
- How we judge it
- Return visits, use outside office hours, and answers checked against the organization's own
- The bet
- Reliable answers in the newcomer's language at any hour will free staff time for the cases that need a person, without lowering the trust the organization has earned.
-
Knowledge pipelineJul 2026 –
- Stage
- In use · builds the SettleSMART knowledge base
- My role
- Product lead: the problem, the rules and the quality bar
- Measure
- 10,000+ cleaned pages and 500+ PDFs from 60+ organizations
- The bet
- Rules with tests, not a model, will give the chatbot a knowledge base that can be audited line by line.
-
Tiny NextAug 2026 –
- Stage
- Live since 15 October 2026 · more than ten friends testing
- My role
- Creator: the idea, every product call, and the testing
- Team
- Solo
- Early result
- 57 live answers graded by hand; none invented where no note existed
- The bet
- Notes come back on a rule you can read on the screen, and a guess is never shown as a fact.
-
RubixoJul 2026 –
- Stage
- Working end to end · the software part of a bigger idea
- My role
- Product lead, with a friend: the thesis, the privacy model and the process
- Team
- Built with a friend
- North star
- Verified valuable outcomes per 100 active members
- The bet
- A trusted intermediary who proposes introductions with a written reason beats an open directory.
-
On Premises AIFeb 2026 –
- Stage
- Two products built
- My role
- Co-Founder
- Team
- Two co-founders
- Focus
- Security, and no dependency on internet connectivity
- The bet
- Organizations with sensitive knowledge need private AI that is secure and keeps working with no internet connection.
-
Green Oak2009 – 2022
- Stage
- Thirteen years in business, 2009 to 2022
- My role
- Co-Founder & Product Manager
- Measure
- 600% revenue growth
- The bet
- One workshop could serve homes and businesses together, and each market would teach the other.
Before and after
One picture per claim
Prioritization · SettleSMART
What to build first
Nine pieces of SettleSMART work and two we parked, placed by how much they matter to newcomers and how hard they are to build.
01 · Start here
Quick wins
High impact, low effort. Done as soon as there was room.
- Make sign-up easier
- Crisis lines when a reply is blocked
- Separate conversations, with history kept
02 · Plan carefully
Big bets
High impact, high effort. Scheduled and staged.
- Interface languages as labelled machine drafts
- Rebuild the knowledge base from 60+ organizations
- Voice input and read-aloud, with budgets
- Email a copy of an answer, with limits
03 · When there is room
Fill-ins
Low impact, low effort. Done between bigger work.
- A "replies to you" page
- Room order set by moderators
04 · Not now
Parked
Low impact, high effort, with the condition that would reopen each.
- Notifications: we would add them if people ask for them
- A shared database across organizations: when there is demand
Decision log, across the work
What was chosen, when, why, and what followedNo.WhenWhereDecisionWhyWhat followed
012009–2022Green OakServe both B2B and B2C marketsOne workshop could serve both with one product line, and each market would teach the other.Both markets were served through to 2022, and together they gave the company financial resilience through inflation.
022024Immigrant TechiesRun talent intake like a technical hiring process, and form teams from the interviewsTeams formed from the interviews and the project's needs have the full shape of a software company.Thirteen MVPs, one per team.
03Feb 2026On Premises AIMake control, of data, infrastructure, cost and connectivity, the product's core promiseOrganizations with sensitive data need to keep it off a shared cloud.The software runs on the organization's own infrastructure, including air-gapped sites.
04Jun 2026SettleSMARTGive the pilot its own environment, separate from the main productThe pilot needed regular changes, while the main product followed its own review and release schedule.The pilot stayed in step with the main product.
05Jul 2026Knowledge pipelineRules with tests decide what is knowledge, never a modelAbout 17,000 pages per run: a model costs credits and cannot be audited line by line. A rule makes the same mistake every time, so it can be found and fixed.Every cleaning rule carries a test that reproduces the real page it came from.
06Jul 2026RubixoStart with one narrow service areaSo one full introduction loop could be tested end to end. Rejected: a general profile database, because more profiles would not show whether introductions work.The full introduction loop was built end to end.
07Oct 2026Knowledge pipelineHunt for losses by random sample against the live page, not by junk scan aloneA junk scan cannot catch a deletion.The office-hours line was caught this way.
08Oct 2026Tiny NextChoose the model that reads a note by measurement, and remove the engines that lostThirteen models on the same thirty notes with one scorer.A third of the source was removed, every test green.
The template
How a finding becomes a requirement
Four columns. The "because" column records why a requirement exists, so a developer can question it.
| Finding | Evidence | So the product must | Because |
|---|---|---|---|
| A detector built for broken PDF fonts judged an office-hours line "garbled", because 8:30am–4:30pm looks like nonsense to it | Random-sample audit, round seven, November 2026 | A rule with a test that reproduces the real page; before every commit, run old and new cleaner on 700 random pages and read every dropped line | For a newcomer, a missing phone number or office hour is worse than a stray menu. |
| A flagship model lost to cheaper models on a reading test | Measurement page, 30 hand-labelled notes | Fix the instrument first: align labels to the prompt's definitions, record the reasoning level each model ran at | Five of seven "misses" were literal readings of an ambiguous prompt. |

