Leaderboards
Minutes is its own metric.
Toggle Miles · Minutes · Steps on every board. Walking + Running split on minutes, and Skating / Fitness / Yoga / Other gained their own lenses.
HealthCode®
Board Meeting · Part Two · June 26, 2026
From the table
to the plan.
May 29 mapped where we stand. Today turns that map into decisions, owners, and dates.
Devs On Tap
·
Convergent half
Why we're here
Last time we mapped the room. Today we make the calls.
Four blocks. None of them re-debate May 29 — each one moves something from "where the board stands" to "what we're doing about it."
- Recap What we heard on May 29. Quick walk through the synthesis — what converged, what diverged, what the room itself flagged to fix.
- Block A What we built in v3. Minutes as a first-class metric stopped being a hypothesis sometime in early June. Quick live tour.
- Block B Steps + synthetic miles. The one beyond-miles decision still on the table. Two paths; one to recommend.
- Block C First SaaS partner & 90-day plan. The bet is locked. Today picks who, who owns the conversation, and by when.
What's locked coming in — not re-debated today
Three things already decided by May 29.
- Single 12-month bet: paid SaaS for orgs. Pulse 4.75/5; 3 of 5 forced-bet votes; 5 of 5 "win" answers cite revenue / funding.
- Win condition: funded and operating. Sustainable revenue with enough margin to hire and pay staff — Steve's framing, the only one who named the spending half.
- The unit is the organization, not the individual. Steve, Stefanie, Helen, and Brian all framed the problem around orgs / groups. Individuals are a funnel, not the product.
Recap
What we heard.
Four forms, five attendees plus two stragglers.
Pulse polls — the three big questions
One lock, one split, one funding question.
1 — Not at all5 — Absolutely
Mean
SaaSIs a paid tier our path to sustainability?
4.75n=4
Beyond milesHow far should wellness go?
3.00n=4
Apple HealthHow urgent is a native build?
3.60n=5
SaaS is essentially unanimous. Beyond miles is the only full 1–5 spread we got — the question Block B has to land. Apple Health leaned more urgent than expected, but it's a funding question, not a strategy question (slide 9).
If we could fund only ONE bet
The room picked SaaS.
Three of five chose SaaS as the one bet to fund. The two outliers picked Apple Health and FundDash — both real, both visible later in this deck.
And every single "what does a successful year look like" answer named revenue or sustainable funding. That's the alignment we build on.
3/ 5
Paid SaaS for orgs
1/ 5
Native / Apple Health build
1/ 5
Grow FundDash giving
5/ 5
Cited revenue / sustainable funding as the "win"
Two questions — start vs end of May 29
By the end, the room agreed on who. Not yet on why.
What problem does HealthCode solve? — how each person answered before discussion (left), and after (right). By close, organizations / groups had become the shared frame.
Start of meeting
End of meeting
Steve
StartHealthCode delivers a program for organizations to use in support of their employees.
EndWe empower people to live healthier lives through goal-based activity challenges … which needs to transition to support overall wellbeing.
Stefanie
StartAn easy-to-use platform to help individuals and organizations of all sizes promote a healthy lifestyle.
EndAn option for organizations of all sizes to engage groups in healthy living.
Helen
StartFor HR wellness teams, a low-cost group tracking tool to drive physical activity.
EndHow to motivate employees / users — tracking of group challenges.
Ayan
StartFree platform for people to get excited about being physically active.
EndFree platform to enter physical activity and get engaged.
The advantage answers, though, mostly stayed at "free" and "easy to use." Nobody independently named our actual moat (integrations, multi-org network, FundDash, ops, trust). That's the positioning gap on slide 8.
The positioning gap
If we can't name the moat, neither can our customers.
Identify ideal client profiles, agree on primary messaging and value prop.
Helen · end-of-meeting validation note
Helen wrote the assignment for us. Today we flag it — it lands in the 90-day plan as a working session, not a board-meeting workshop.
Apple Health · closing the loop
A funding question, not a strategy question.
- The pulse landed at 3.6 — more urgent than expected. Helen even picked it as her one bet.
- Apple gate-keeps HealthKit behind native apps — a web solution isn't an option. The only path to Apple Health data is a native iOS build.
- But we can't act on it tomorrow regardless. There's no budget for the native build, and no budget for the ongoing iOS / HealthKit maintenance it would create.
- Decision: deferred until funded. Earmarked in the SaaS revenue plan; we'll define the trigger in Block C (sponsor, paid-tier MRR threshold, grant).
What we're not doing today: re-opening the native-vs-not debate. The data and the funding gate together close the loop. We move on.
Block A
What we built in v3.
The May 29 deck floated minutes-as-first-class as a hypothesis. In the four weeks since, most of it shipped.
The shift, made real
Minutes stopped being second-class.
May 29
Miles as the universal metric
- Yoga, weight lifting, gardening converted to a synthetic "mile equivalent"
- Leaderboards favored runners and cyclists by construction
- Non-distance athletes had no natural goal at registration
- Exports to partner orgs missed half the picture
→
Today
Minutes is a peer of miles
- Every leaderboard carries miles and minutes ranks
- Walking and Running split on minutes; Skating, Fitness, Yoga, Other got their own minutes lenses
- Org-event Sheets export gained a minutes column
Inside the app
What landed since May 29.
Seven donor-visible updates across leaderboards, goals, trackers, privacy, and checkout.
Goals
Goals replaced — and multiplied.
Every goal now carries a cadence, metric, value, and optional activity type. Members can set as many as they want — not a single event-long mile goal.
Trackers
Trackers got their own home.
A dedicated trackers page plus a per-tracker diagnostics view — last sync time, sync cadence, and what activity actually came through.
New tracker
Google Health, live.
Our newest tracker integration — and the path forward. Will replace Fitbit in September when Fitbit's old API sunsets.
Privacy
Leaderboard privacy in the profile.
Hide-from-leaderboards is now a User Profile setting — discoverable and editable, not a one-time choice buried in the old "group account" registration step.
Checkout
Org auto-fill at checkout.
Email domain detects the registrant's organization automatically. No scrolling a dropdown to find their employer.
Payments
Cover-the-fee on donations.
Donors can opt to cover the Stripe transaction fee, so more of their gift reaches HealthCode.
The implicit vote
The May 29 v3 line — already shipping.
We're not asking the board to authorize a new direction. We're showing what's already running — and asking the room to object if anything on screen doesn't belong.
Silence is the ratification.
- In v3: minutes as a first-class metric.
- Not in v3: sleep, nutrition, meditation, lifestyle-tracking expansion. Deferred, not declined — revisit once v3 has paying customers funding the expansion.
- The product filter holds: if a tracker already does it, we don't.
Block B
Steps & synthetic miles.
The one beyond-miles decision still parked.
The complaint
Several users, including a board member, said we were double-counting.
Wear a tracker on a walk. The tracker logs the walk explicitly, and the day's total step count includes those same steps. We ingest both — the explicit walk plus a synthesized Walk row from the day's steps. Mileage shows up inflated.
The proposal
- Introduce a Daily Steps activity type and a steps metric. Tracker daily roll-ups would write as Daily Steps rows instead of synthetic Walks.
- This clarifies where the miles came from, but we'd still apply synthetic miles and minutes to those rows — so the double-counting concern doesn't fully go away.
- It does open the door to including steps in leaderboards and goals — orgs could run step-based contests if they want.
The values question
Where do we draw the line between activity and ambient movement?
When meditation came up earlier as a candidate, the line was clear: physical activities belong in one bucket; wellness activities belong in another. Concern was expressed about lumping them in together.
Daily ambient steps — walking around your kitchen, walking to the mailbox, walking from a parking lot — sit on the same side of that line as meditation does. Baseline movement. Not deliberate exercise.
If meditation doesn't belong in the physical-activity bucket because it's a different kind of thing, neither do daily ambient steps.
The principle, applied consistently
The path forward
Two paths.
"Synthetic miles" = any miles figure that wasn't from an explicitly-logged distance activity i.e. yoga via MET.
Option A · Riskier
Rip the band-aid.
- Stop applying synthetic miles — steps stand fully on their own.
- Step-only users disappear from miles boards and instead appear on Steps boards. Their totals shift from Miles to Steps overnight.
- Higher chance of silent disengagement — the failure mode that matters most.
- Stays available as a possible future direction if Option B doesn't land.
Option B · Recommended
Attribute, and watch.
- Keep applying synthetic miles — mile totals don't change.
- Tracker daily roll-ups show up as Daily Steps, not as a phantom Walk row.
- Hypothesis: proper attribution might be enough to clear up any confusion.
- If it doesn't, Option A is still available — with real data behind the call.
Regardless of path: the org-event export gains parallel rollups — miles, minutes, and steps as three columns — so org admins see all three and pick what they want to surface.
The ask
Endorse Option B — we attribute, then watch.
- Daily Steps activity type and the steps metric come online behind a controlled rollout.
- Synthetic miles keeps being applied — mile totals don't move; step-only users stay on existing boards.
- Org-event export gets parallel miles / minutes / steps rollups.
- Monitor whether the double-counting complaints continue once attribution is clear. Revisit at the next checkpoint with data.
If the answer is no: nothing changes — donors see exactly what they see today. We capture the specific blocker plus what would unblock it, and revisit at the next checkpoint.
Block C
First SaaS partner. 90-day plan.
The whole point of locking the SaaS bet was to clear the way for this conversation. Pick a lead. Pick a backup. Name an owner. Set a date.
Where we left the strawman
The tier shape from May 29 — still the working hypothesis.
| Tier | For whom | What's in it | Illustrative price |
|---|---|---|---|
| Community | Anyone — today's free experience. | Join HealthCode-wide events, track activity, see leaderboards. Unlimited seats. | $0 |
| Workplace | HR / wellness lead, self-serve, 50–1,000 employees. | + private org events, branding, dashboards + CSV, FundDash org campaign, threshold incentives. | ~$1,200–7,500 / yr by band |
| Partner | Austin-scale — 1,000+ / enterprise. | + full white-label, SSO / HRIS, co-branded CSR reporting, dedicated CSM. | Negotiated |
Open knobs — paywall line, pricing axis, FundDash positioning, V1 engagement levers — are the first-partner conversation's job to validate, not the board's job to settle today.
First paying partner — who?
Pick one lead, one backup.
From the recurring core. For each candidate — what budget? Who's our champion inside? What would they need to say yes?
- Flagship · high-leverage City of Austin. Left and came back — engagement-as-moat testimonial. Big if it lands; high-stakes if it sours. Public-sector procurement.
- Lowest-friction yes Friedkin Group. Already gives ~$12–17 per registrant. Corporate, smaller volume, easier procurement than public sector.
- The wedge tier OK State Gov't · Clay County · Parkway · Avery. The mid-market public-sector wedge the Workplace tier is designed for. Cheaper signal, lower stakes, more procurement.
90-day plan · the output of today
Every decision needs an owner and a date.
| Action | Owner | By |
|---|---|---|
| First SaaS partner — lead (from slide 21) | — | — |
| First SaaS partner — backup | — | — |
| Workplace tier — scope V1 features, settle pricing axis + bands | — | — |
| Positioning + ICP working session (Helen's ask) | — | — |
| Apple Health — define the "funded" trigger | — | — |
| Next checkpoint meeting | — | — |
From the table to the plan.
Decisions & owners · in writing within 48 hours