Releases

Everything shipped, and how it was built.

Two timelines, both grouped by milestone. The first walks the releases newest first — every milestone says what that step of the product delivered, and lists the versions inside it. The second groups the documents the product is built on. Nothing here is a projection — it is all read from files that exist.

NEW
v124

Latest release

The brief detail finally lands in the right panel.

v124 (28 Oct 2026) fixed the real bug underneath months of work: the saved-brief detail was being painted into the composer pane, not the brief pane. Now the composer is always new, the detail opens inside the Briefs panel, and the News and Releases pages ship live, source-attributed content. Every line above is read from the packaged build’s own manifest — nothing is invented.

The journey from 2025

Fifty-six packaged builds across twelve milestones, from the first landing page to a live, multi-role product. Each node is a milestone; the labels below carry its version range and what it delivered.

2025 · Foundations2026 · Build-outOct 2026 · Now1v36–v472v48–v623v63–v694v70–v745v75–v776v78–v857v86–v1008v101–v1049v105–v10810v109–v11311v114–v11812v119–v124
M1v36–v47Landing foundations & first deploy
M2v48–v62Scoring engine & real backend
M3v63–v69The board becomes a product
M4v70–v74Cross-page consistency & investor board
M5v75–v77The multi-role workspace
M6v78–v85Honest samples & free AI engine
M7v86–v100Role-aware dashboard & BC Points
M8v101–v104Rewards, Marketplace, legal
M9v105–v108Marketplace flow & named dashboards
M10v109–v113One rhythm everywhere
M11v114–v118Workspace information architecture
M12v119–v124News, Releases & brief detail

Release timeline

Releases are grouped by milestone — a step in how the product changed — rather than listed as one flat, undated stream. The date beside a version is the modification date of that build’s manifest; the line beside it comes from the manifest’s own version section. Where a manifest records no line for a version, we say so rather than invent one.

56 packaged builds · v69 to v124 · 12 milestones

Milestone 12News, Releases, and how the brief detail worksv119–v124

The News and Releases pages arrive, and every role lands on a default tab that suits it. Most of the work in this step is one question — where does a saved brief actually open? — which is answered three times before it is answered right: v120 renamed the composer, v121 opened the brief inside the Briefs panel, v122 tried a dedicated tab, and v123 went back to in-panel. v124 finally fixed the real bug underneath all of it (the detail was being painted into the composer pane, not the brief pane, because the code targeted the wrong element) and added a genuine click test as the second gate layer.

  1. v12428 Oct 2026
    the brief detail actually opens in the Briefs panel; the composer is always new; the news page photos are now product imagery
  2. v12327 Oct 2026
    detail opens INSIDE the Briefs panel (same tab); the broken Brief details tab is gone; the composer can never be hijacked
  3. v12227 Oct 2026
    a dedicated "Brief details" TAB, the investor leads page re-styled to match the role pages
  4. v12127 Oct 2026
    the saved-brief room is the Briefs panel, investor demand notes, wider margins, a livelier News
  5. v12027 Oct 2026
    brief->board with no reload, real brief details, visible per-role default, Releases page
  6. v11927 Oct 2026
    no more wiggle, Introduction first, a default tab per role, honest points
Milestone 11Workspace information architecturev114–v118

The workspace stops being one long page and becomes a set of rooms. Briefs becomes a tab instead of a scroll position, the side rail becomes display-only rather than a second set of controls, each role gets an Introduction panel that explains itself, and the rail is stripped down until it says only two things: your role, and your points.

  1. v11827 Oct 2026
    the rail is exactly: your role, your points
  2. v11726 Oct 2026
    an Introduction panel per role, a summary rail, a queue that explains itself
  3. v11626 Oct 2026
    one card size, no frames, Account and Points as panels
  4. v11526 Oct 2026
    one consistent right panel, Briefs as a tab, an information-only rail
  5. v11426 Oct 2026
    constant content to the rail, role switching back to the header, the brief list on top
Milestone 10One rhythm everywherev109–v113

One spacing rhythm is applied across every page, and the workspace is made to fit a phone properly. The rule that comes out of this step is "counts tell the truth": several count bugs are fixed rather than papered over, and reward claims that could not be honoured are deleted instead of reworded.

  1. v11323 Oct 2026
    the board stops looking cramped, the audience pages stop looking empty, and the tester flow goes somewhere
  2. v11222 Oct 2026
    the workspace makes sense, the counts tell the truth, and the brief tool delivers
  3. v11121 Oct 2026
    one menu, a workspace you can use one-handed, and two pages that match
  4. v11021 Oct 2026
    One spacing rhythm everywhere, and the workspace fits a phone
  5. v10921 Oct 2026
    No change description recorded for this version.

The manifest for v109 carries another version’s heading (it is filed as v107), so v109 is listed above with no description rather than borrowing a line that belongs to a different build.

Milestone 9Marketplace flow and named dashboardsv105–v108

One role now means one named dashboard — Founder studio, Investor board, Tester desk — so nobody has to guess which room they are in. The marketplace reads as one sequence instead of three screens, the listing error tells you what to do next, and the mobile navigation stops covering the content it sits on.

  1. v10820 Oct 2026
    No change description recorded for this version.
  2. v10720 Oct 2026
    The sell card tells the truth, and your briefs are where you left them
  3. v10620 Oct 2026
    One role, one named dashboard, one predictable navigation
  4. v10520 Oct 2026
    The listing error tells you what to do, and the marketplace reads as one sequence

The manifest for v108 is filed under v107’s heading, so v108 has no description of its own and is marked as having no record rather than inheriting v107’s line.

Milestone 8Rewards, Marketplace, legal, and server-side trustv101–v104

The rewards section lands on the public site and tester responses start acting on their own selection. The important change is underneath: points stop being written from the browser and move behind the award-points Edge Function, so a balance is something the server awards rather than something a page claims. The marketplace page and the legal pages are added in the same step.

  1. v10419 Oct 2026
    The marketplace stops being a page and becomes a product
  2. v10319 Oct 2026
    Mobile layout repair: the landing page finally behaves on a phone
  3. v10219 Oct 2026
    Each tester response now acts according to its own selection
  4. v10119 Oct 2026
    Rewards section on the landing page + real response actions in the app
Milestone 7Role-aware dashboard and BetaConnect Pointsv86–v100

One role gets one focused dashboard, and BetaConnect Points become a real ledger (points.sql) with a fixed meaning: 100 BP is $1 tracked, not payable. This step also contains the lesson the team keeps: v86, v87 and v88 were edited in the wrong file, because workspace.html — not the dashboard page being looked at — is what the signed-in app actually loads. v89 and v90 are the corrections.

  1. v10014 Oct 2026
    stable role switching (no more jumping) + constant rail width + visible rules
  2. v9814 Oct 2026
    No change description recorded for this version.
  3. v9714 Oct 2026
    two real defects found by reading the code (hidden points panel; drifting panes)
  4. v9614 Oct 2026
    complete package: every dashboard fix + the line-ending repair
  5. v9514 Oct 2026
    scroll-consistent layout + sample leads in every panel + BetaConnect Points
  6. v9414 Oct 2026
    navigation bar cleanup: duplicate Log out removed, persona row made even
  7. v9314 Oct 2026
    layout consistency: aligned top bar + dedicated Tester panel
  8. v9214 Oct 2026
    "Load 3 sample briefs" for testing
  9. v9114 Oct 2026
    fix the dead "Show this to investors" toggle
  10. v9014 Oct 2026
    ship the dashboard fixes to workspace.html + align the tests with role-aware
  11. v8914 Oct 2026
    ship the dashboard fixes to the file the app actually loads (workspace.html)
  12. v8814 Oct 2026
    the investor board is strictly investor-only (role-clarity fix)
  13. v8714 Oct 2026
    clearer, simpler investor board (fix the double display)
  14. v8613 Oct 2026
    role-aware dashboard shell (one role = one focused tool)

Two honest gaps here: there is no deploy-ready-v99 folder, so v99 is absent from this list entirely; and the manifest for v98 is filed under v107’s heading, so v98 carries no description of its own.

Milestone 6Honest samples, a full-stack audit, and a free AI enginev78–v85

The board looked dead until a founder published, and the fix was refused: rather than invent leads, sample rows ship behind SAMPLE chips so no one mistakes them for demand. A full-stack audit produces the contrast fixes, the brief editor gains an engine selector, a scaffold for real third-party model providers is built, and Groq is added so scoring works without anyone having to pay first.

  1. v8513 Oct 2026
    single-selection fix in the scoring-engine picker
  2. v8413 Oct 2026
    a genuinely free engine (Groq) so the AI review works without payment
  3. v8313 Oct 2026
    honest engine-chip wording (a provider key IS configured)
  4. v8209 Oct 2026
    scaffold for real third-party LLM engine connections
  5. v8109 Oct 2026
    fix the expand/collapse layout chaos on the brief tool
  6. v8009 Oct 2026
    the full brief editor and the engine selector
  7. v7909 Oct 2026
    accessibility fixes and first-screen clarity, from a competitive teardown
  8. v7809 Oct 2026
    The board is empty until a founder publishes, which left the page looking dead.
Milestone 5The multi-role workspacev75–v77

Other people exist in the product now. The data layer is split into MY_BRIEFS and BOARD_BRIEFS so a brief someone else published can never appear in "yours", roles become a set you hold rather than a radio button you pick, briefs get shareable links, and the public navigation is renamed from "Investor board" to "Investor leads".

  1. v7708 Oct 2026
    Investor board -> Investor leads, everywhere the link appears in the public navigation, the mobile menu and the footer of all six public pages.
  2. v7608 Oct 2026
    This is the growth loop the product was missing.
  3. v7508 Oct 2026
    The first v75 built the persona layer but left it invisible to every account that existed before it.
Milestone 4Cross-page consistency and the investor boardv70–v74

The navigation is unified across every page and the footer is unified with it, so the site stops reading as six different products. investors.html and deals.sql are created so the third audience — investors — has a product of its own rather than a paragraph on someone else’s page.

  1. v7407 Oct 2026
    No change description recorded for this version.
  2. v73b07 Oct 2026
    No change description recorded for this version.
  3. v7307 Oct 2026
    No change description recorded for this version.
  4. v7206 Oct 2026
    No change description recorded for this version.
  5. v7106 Oct 2026
    No change description recorded for this version.
  6. v7006 Oct 2026
    No change description recorded for this version.

None of the manifests from v69 to v73b carry a version heading, so every build in this band is listed as having no recorded description rather than being given an invented one.

Milestone 3The board becomes a product, and the landing rebuildv63–v69

A duplicated <style> tag is root-caused as the reason raw CSS appeared on screen, and the landing page is rebuilt from a competitive teardown. The fabricated statistics and fake testimonials are deleted outright; v68 rebuilds Voices from real customer interviews, keeping roles, cities and months but no names. v69 promotes the brief tool to its own page, brief.html.

  1. v6902 Oct 2026
    No change description recorded for this version.

Only v69 has a packaged build in this repository. v63–v68 predate the earliest deploy-ready package here (v69), so there are no version rows to list for them — and v69’s own manifest carries no heading.

Milestone 2A deterministic scoring engine and a real backendv48–v62

The AI Pre-Test Brief appears, carrying the honesty line the product still keeps: "Estimated readiness — a starting point, not a verdict." Supabase Auth is adopted as the real backend, and the scoring engine is expanded so it reads differently per industry instead of scoring every startup the same way.

No packaged build folder survives from v48–v62. The earliest deploy-ready package in this repository is v69, so this step is described from the record and no version rows are listed.

Milestone 1Landing page foundations and the first deployv36–v47

Login and signup modals, a three-step checkout priced in CAD, and the first deployment — EdgeOne first, then Cloudflare Pages. The failures in this band are the ordinary ones and are recorded as such: a duplicate const name and a carousel TypeError.

No packaged build folder survives from v36–v47. The earliest deploy-ready package in this repository is v69, so this step is described from the record and no version rows are listed.

How this was built

The planning and design documents behind the product, grouped by the stage of the work they belong to, with the dates recorded on each file. They are listed as plain filenames on purpose: these files live in the repository but are not part of the deployed package, so a link here would only 404.

Stage 1Business and financial foundationsBusiness plan · financial forecast

The plan the company is run against and the numbers it is measured against.

  1. Business plan20 Oct 2025
    • 20 Oct 2025BetaConnect - Final Business Plan.pdf
    • Financial forecast16 Oct 2025
      • 16 Oct 2025BetaConnect - Financial Forecast.pdf
Stage 2Customer research and validationValidation report · user profiles

Who the customer is, stated from research rather than from assumption — the profiles describe roles, cities and months, and carry no names.

  1. Customer validation report16 Oct 2025
    • 16 Oct 20252. Customer and Market Validation/BetaConnect - Customer Validation Report .pdf
    • Customer user profiles08 Apr 2025 / 16 Oct 2025
      • 16 Oct 20252. Customer and Market Validation/BetaConnect - Customer User Profiles.pptx
Stage 3Product designDesign deck · walkthroughs · design source

What the product is meant to look like and do, including the recorded walkthroughs for beta testers and for startups and incubators.

  1. Product design deck16 Oct 2025
    • 16 Oct 20253. Product Design/Product Design Deck/Copy of BetaConnect - Design Deck.pdf
    • Product walkthrough recordings16 Oct 2025
      • 16 Oct 20253. Product Design/BetaConnect - BetaTesters.mp4
      • Figma source file16 Oct 2025
        • 16 Oct 20253. Product Design/Figma Exports/BetaConnect.fig
Stage 4BrandLogo variation · brand snapshot

The visual identity and the one-page snapshot it is summarised on.

  1. Logo and brand variation16 Oct 2025
    • 16 Oct 20253. Product Design/Branding/Beta Connect logo variation 1.pdf
    • Brand snapshot19 Jun 2025
      • 19 Jun 20254. Technology Roadmap and Architecture/Copy of Beta Connect Brand Snapshot.pdf
Stage 5Technology plan and roadmapTechnology plan · roadmap deck

The architecture the build milestones were executed against.

  1. Technology plan16 Oct 2025
    • 16 Oct 20254. Technology Roadmap and Architecture/BetaConnect - Technology Plan.pdf
    • Technology roadmap deck16 Oct 2025
      • 16 Oct 20254. Technology Roadmap and Architecture/BetaConnect- Technology Roadmap.pptx

These are the dates recorded on the files themselves, not authoring dates. Several carry the same 16 Oct 2025 timestamp — the signature of a bulk import — so those dates say when the files arrived here, not when they were written. Nothing else is claimed about their contents.

Vision, mission, values

Three statements that have guided every build since 2025 — stated plainly, and only what the product actually does.

Vision

A world where every early-stage founder can prove demand with real users before they spend a dollar of runway — and where the testers and investors who supply that signal are rewarded for it.

Mission

The validation layer for early-stage startups. Score assumptions first, then build the evidence before you build the product.

Values

  • Real over fake. Sample leads are marked SAMPLE and never shown as proof; nothing is fabricated.
  • On-device ledger. Every point is a keyed entry written to this browser, and each action pays once; the running total is derived from those entries.
  • Built in Canada, for Canadian startups. Proudly building for Canadian founders, testers and investors.

Welcome back

Log in to your BetaConnect account.

Forgot password?

No account? Sign up

Create your account

Start with a free simulated pre-test brief.

Already registered? Log in

Pro Plan

$300 /month CAD

Illustration only$300.00 CAD
Illustrative HST (not charged)$39.00 CAD
Illustrative total$339.00 CAD

Demo checkout — no card is charged.

Privacy Policy

BetaConnect Inc. · Effective September 29, 2026

Plain-language summary

The full, current Privacy Policy and Terms of Service live on our Legal page. This summary is provided for convenience only.

1. Who we are

BetaConnect is a validation layer for early-stage startups: founders score a brief, testers answer back, and investors review the evidence.

2. What we collect

We keep this deliberately small:

Your password is handled by our authentication provider using industry-standard hashing. We never store or see it in readable form.

3. Why we collect it

We use this information to create and secure your account, to deliver and support the service, to communicate with you about beta access, service changes and your support requests, to understand which parts of the product people actually use, and to detect abuse. We do not sell personal information and we do not share it with advertisers or data brokers.

4. Your consent and your rights under PIPEDA

We handle personal information under the Personal Information Protection and Electronic Documents Act (PIPEDA), Canada’s federal privacy law, and we rely on your consent to do so. Under PIPEDA you have the right to access the personal information we hold about you, the right to have it corrected where it is inaccurate or incomplete, and the right to withdraw your consent at any time, subject to legal or contractual limits and to reasonable notice. You may also ask us to delete your account and the information tied to it. If you withdraw consent we may no longer be able to provide the service. We aim to answer every request within thirty days. If you are not satisfied with our response you may complain to the Office of the Privacy Commissioner of Canada.

5. Who else processes your information

We use a small number of infrastructure providers, which act on our instructions and are not permitted to use your information for their own purposes:

Support staff at these providers may access data outside Canada in the ordinary course of keeping their systems running.

6. Cookies

Cloudflare Web Analytics is cookieless: it does not set or read cookies and it does not build a profile that follows you between sites. We set no advertising cookies and no cross-site tracking cookies. We do use your browser’s local storage to remember practical things such as your chosen colour theme, your signed-in session, and waitlist entries waiting to be saved.

7. How long we keep it, and how we protect it

We keep account and waitlist information while it is still needed for the purpose we collected it, and we delete or de-identify it within a reasonable period after you close your account or ask us to remove it. We may retain minimal records longer where law, tax or accounting rules require it.

We are an early-stage product, so we will be honest about the level of protection rather than overstate it: the site is served over HTTPS, passwords are hashed by our authentication provider and never stored by us in readable form, database access is restricted, and administrative access is limited to the founders. Even so, no system is perfectly secure, and we do not promise that this one is.

8. Children

The service is a business tool and is not directed at children under sixteen.

9. Changes to this policy

We will post any updated version on this page and change the effective date above. If a change is significant we will also try to tell you directly.

10. Contact us

Questions, access requests and complaints: privacy@betaconnect.ca. BetaConnect Inc., Toronto, Ontario, Canada.

Terms of Service

BetaConnect Inc. · Effective September 29, 2026

Plain-language summary

The full, current Privacy Policy and Terms of Service live on our Legal page. This summary is provided for convenience only.

1. Acceptance of these terms

By visiting this site, creating an account or using BetaConnect, you agree to these terms. If you do not agree, please do not use the service. If you are using it on behalf of a company, you confirm that you may bind that company to these terms.

2. The service, and the fact that it is a beta

BetaConnect is a validation layer for early-stage startups: founders write and score a brief, testers answer back, and investors review the evidence. Today the AI Pre-Test Brief and its deterministic five-person simulated panel are live; real tester responses and investor-ready evidence are planned, not live yet. What the AI Brief produces is a simulation, not feedback from real people.

The service is an early-access beta and a working prototype. It is incomplete, it changes often, features may be added, altered or removed without notice, and it will contain bugs. Data you enter during the beta may be lost or reset. Please do not rely on the beta as your only record of anything important, and do not use it for anything where a failure would cause real harm.

3. Your account

You agree to give us accurate registration information and to keep it up to date. You are responsible for safeguarding your password and for everything that happens under your account, and you should tell us promptly at hello@betaconnect.ca if you think your account has been used without your permission. One person or one company may hold one account unless we agree otherwise in writing.

4. Pricing is information only — no payment is processed

The plans shown on this site (currently $100, $300 and $500 CAD per month) are displayed for information and evaluation only. No payment processing is live. The checkout screens are simulated: no card is captured, no card is charged, no invoice is issued and no subscription is created. If and when we begin charging, we will present real payment terms and get your agreement before taking any money.

5. Acceptable use

You agree not to use the service to break the law, to infringe someone else’s rights, to upload material you have no right to upload, to send spam or malware, to scrape or copy the service at scale, to reverse engineer it, or to get around its security or access limits. We may suspend or end access if you do.

6. No warranty

The service is provided “as is” and “as available”, with all faults and without warranty of any kind, whether express or implied. To the fullest extent the law allows, we disclaim every implied warranty, including merchantability, fitness for a particular purpose, non-infringement, uninterrupted availability, and the accuracy or completeness of any output, score, estimate or recommendation the service produces. Nothing here is a promise of any particular business result.

7. Limitation of liability

To the fullest extent the law allows, we are not liable for any indirect, incidental, special, consequential, exemplary or punitive damages, or for any loss of profit, revenue, data, goodwill or business interruption, arising out of or relating to your use of the service, even if we were told such loss was possible. Our total aggregate liability for all claims relating to the service is limited to the greater of one hundred Canadian dollars (CAD $100) and the amount you actually paid us for the service in the twelve months before the claim. Some jurisdictions do not allow these limits, so parts of this section may not apply to you.

8. Your responsibility to us

You agree to cover reasonable losses, including legal fees, that we incur because of your breach of these terms or your misuse of the service.

9. Changes, suspension and termination

We may modify, suspend or discontinue all or part of the service at any time, including during the beta, and we do not guarantee it will stay available. You may stop using it at any time. We may also update these terms; the current version and its effective date always live on this page.

10. Governing law

These terms are governed by the laws of the Province of Ontario and the federal laws of Canada that apply within it, without regard to conflict-of-laws rules. You and we submit to the exclusive jurisdiction of the courts of the Province of Ontario for any dispute arising out of these terms or the service.

11. Contact us

Questions about these terms: hello@betaconnect.ca. BetaConnect Inc., Toronto, Ontario, Canada.