The active
build board.
A public view of what is moving, what is being sharpened, and what is waiting for the right moment.
Live
3
Final Beta
1
In Progress
2
Domains
QA / SaaS / Mobile / Education / Games
Six lanes, one operating system.
TestFLY
Test management and companion overlay
- CSV test case imports, section organization, test runs and assignments, reporting, workspace access, and the TestFLY Companion overlay.
Hourkeepers
Workforce hours and approvals
- Timesheet submission, manager approvals, project-scoped access, employee invitations, staffing targets, labor-cost reporting, and organization workflows.
QAtalyst
QA intelligence engine
- QAt triage flows, ticket-to-test-case generation, fast bug and ticket drafting, project memory, terminology awareness, and practical integrations with Jira, TestRail, and Playwright.
Edu-Mates
Educational game platform
- Product shape, learning loop clarity, teacher and parent value, and early platform framing.
GroSharey
Shared grocery shopping
- Shared lists, account access, household collaboration, notifications, and receipt workflows.
Puck King Hell
Arcade hockey game lane
- Core identity, gameplay hook, tone, and production lane definition.
How the lab decides what ships.
Ship useful things
Utility first. If it does not earn a place in a real workflow, it does not earn the polish.
Validate with real workflows
Every lane is tested against actual jobs people do: QA triage, job hunting, creative production, learning loops, and project execution.
Keep proof visible
Status, decisions, and trade-offs are part of the product. The build board is public on purpose.
Avoid fake polish
No motion for motion's sake. No marketing language pretending to be a feature. Surfaces stay honest.
Iterate publicly where possible
Notes, screenshots, and shipped slices over private decks. The lab is the demo.