weekly check-in #2

Founder-led facility onboarding is now the test.

at a glance

vein has the core product and operating pieces in place. The next test is turning warm facility access into posted shifts, completed shifts, and repeat use.

current status

Production-ready service stack tech vein has moved beyond MVP into a production-ready operating base.

vein admin app live tech The team can manage service operations from an internal admin surface.

LINE OA base is growing tech 42 providers and 6 facilities are connected through LINE OA.

Onboarding has started business 34 providers and 1 facility are onboarded.

Active facility demand business 1 facility has an active posting.

Landing page ready tech The public front door is ready for credibility and inbound traffic.

Daily content engine running tech Facebook and Instagram posting are running daily.

Social channels set business The main social channels are in place for provider and facility communication.

Facility lead engine ready tech 800+ ready-to-contact facilities are available for founder-led outreach.

moved this week

Cold outreach started business 8 facilities reached; 2 are interested but not yet onboarded.

LINE Scale Up pilot direction business Met with LINE Scale Up Venture; they are looking for a pilot program and LINE Mini App use case.

CloudNurse meeting scheduled business Meeting set with CloudNurse, an EMR service for nursing homes, to explore a pilot path with their customers.

CloudNurse proposal written business Pilot scope, first ask, success bar, and decision path are written for review before the 24 Jun meeting.

Incorporation path prepared business Filing timeline and prep packet are mapped against the Venture Spark deadline.

Liquidity planning business Mapped possible liquidity channels: concierge facility posting, LINE group broadcasting, LINE OA provider pool, social provider acquisition, warm partner access, cold outreach, public shift discovery backup, niche wedge focus, repeat posting, and referral loops.

stuck

Facility self-serve tech The product is not yet pulling facilities in by itself.

Repeat usage business One completed loop is not enough; the next goal is repeatable filled shifts.

Provider activation business Content and provider activation must follow real facility demand, not generic growth.

PDPA concerns tech Data handling, consent, and access controls need to stay clean before broader onboarding.

Business

24 Jun CloudNurse review business Bring the first ask, suitable-facility profile, intro message, and no-integration pilot scope.

Facility onboarding kit business Prepare the first-call script, suitability checklist, and manual handoff flow for warm facilities.

Cold facility backup plan business If the CloudNurse path does not produce facility introductions, use targeted cold outreach to move facilities toward first posted shift.

Incorporate by July business Use the packet and timing memo to move filing before the Venture Spark deadline window gets tight.

Weekly proof scoreboard business Track posted shifts, completed shifts, repeat posting, and attendance confirmation as the weekly proof base.

Tech

Facility self-serve readiness tech Tighten posting, applicant review, acceptance, attendance, completion record, notifications, and access controls so facilities can operate without founder handholding.

Continuous optimization tech Keep improving the facility flow, provider activation, and weekly proof metrics based on each real onboarding attempt.

ask Venture Spark

Comment on company stage and direction business Tell us if our current stage, direction, and next proof path are framed clearly enough.

Review the CloudNurse first ask business Pressure-test the 24 Jun ask: 1-2 suitable facility introductions, no integration, clear pilot success bar.

source trail

21 source files used

STATE.md
56,980 bytes - source body not rendered

AGENTS.md
4,158 bytes - source body not rendered

CLAUDE.md
7,361 bytes - source body not rendered

Claude/TRUTH-SHEETv1.0.0.md
35,282 bytes - source body not rendered

01-Strategy-Fundraising/Meetings/2026-06-19-venture-spark-weekly-update-prep.md
12,082 bytes - source body not rendered

Meetings/2026-06-17-vein-venture-spark-pitch-refinement-03_synthesize.md
11,898 bytes - source body not rendered

Meetings/2026-06-12-vein-venture-spark-pitch-refinement-02_synthesize.md
10,221 bytes - source body not rendered

01-Strategy-Fundraising/2026-06-17-market-sizing-defense-qa.md
4,295 bytes - source body not rendered

04-Growth-Outreach/LINE-OpenChat-Signal/reports/market-intelligence-summary.md
2,008 bytes - aggregate only; source body not rendered

04-Growth-Outreach/LINE-OpenChat-Signal/data/derived/kpi-market-size.json
334 bytes - aggregate only; source body not rendered

04-Growth-Outreach/2026-06-19-liquidity-planning.md
3,459 bytes - source body not rendered

01-Strategy-Fundraising/Partnerships/CloudNurse/2026-06-cloudnurse-x-vein-pilot-whitepaper-internal.md
19,638 bytes - source body not rendered

01-Strategy-Fundraising/Partnerships/CloudNurse/2026-06-cloudnurse-facility-access-pilot-external.md
7,577 bytes - source body not rendered

01-Strategy-Fundraising/Partnerships/CloudNurse/2026-06-24-cloudnurse-facility-access-pilot-deck.html
56,438 bytes - source body not rendered

05-Legal-Compliance/Corporate/2026-06-15-when-vein-should-incorporate.md
11,409 bytes - source body not rendered

05-Legal-Compliance/Corporate/2026-06-15-vein-pre-filled-incorporation-packet.md
24,304 bytes - source body not rendered

02-Product/vein-admin/README.md
8,613 bytes - source body not rendered

04-Growth-Outreach/Content & Social/high-yield-viral-growth-plan.md
27,545 bytes - source body not rendered

FOUNDER-MCP-START-HERE.md
8,565 bytes - source body not rendered

03-Brand-Design/claude-design-pack/README.md
4,042 bytes - source body not rendered

docs/superpowers/specs/2026-06-17-vein-vs-update-dashboard-design.md
10,148 bytes - source body not rendered

weekly check-in #3

Liquidity is now the test.

at a glance

vein has turned the soft launch into a larger owned provider channel and early facility-side interest. The next test is turning that attention into faster facility posting, better shift discovery, applications, and completed loops.

current status

Liquidity test is open business There is now enough owned audience to test whether attention can become real shift activity.

Proof bar has moved business This week should be judged on posted shifts, applications, completed work, and repeat usage, not on whether the product exists.

Posting speed is the bottleneck tech Facility activation now depends on making shift creation fast enough to match the provider audience.

moved this week

Provider OA grew business Soft launch moved the provider LINE OA from 52 to 132.

50+ new platform users business The soft launch brought more than 50 new users onto the platform.

Facility OA also moved business Facility LINE OA gained 6 users, giving the facility side a small but real channel to activate.

Product focus narrowed tech Tech focus is now bug fixing and filtering enhancement so providers can find relevant shifts faster.

Facility posting shortcut defined tech Next facility-side product direction is to let facilities send their usual broadcast text into vein, then have AI structure it into a shift.

CloudNurse decision point reached business The ask is prepared; the verdict is still unknown until the 24 Jun discussion.

stuck

Audience is not liquidity yet business LINE OA growth and new users are strong signals, but they still need to become posted shifts, applications, and completed work.

Facility posting still has friction tech Facilities are not yet posting fast enough on their own; the posting flow still needs to match their existing broadcast behavior.

Product polish before scale tech Bug fixing and filtering enhancement need to stay ahead of wider provider and facility activation.

CloudNurse outcome pending business Carry-forward from Week 2: the ask is ready, but the verdict will not be known until tomorrow.

Business

Record CloudNurse verdict business Carry-forward from Week 2: after the 24 Jun discussion, mark whether this becomes facility introductions, a revised ask, or a closed path.

Activate provider OA and new users business Use the 132-provider OA and 50+ new platform users to push live shift discovery, applications, and provider questions.

Activate facility OA business Use the 6 new facility OA users as the first test group for faster posting and clearer facility onboarding.

Cold facility backup remains business Carry-forward from Week 2: if CloudNurse does not produce facility introductions, use targeted cold facilities to create the next first-post path.

Weekly proof scoreboard business Carry-forward from Week 2: report posted shifts, applications, completed shifts, repeat posting, and attendance-confirmed work once available.

Tech

Bug fixes and filtering tech Current tech focus is stability, cleaner filters, and faster shift discovery before broader distribution.

Facility text-to-shift intake tech Next tech focus: facilities send their usual broadcast text to the facility LINE OA; AI converts it into a structured shift on the platform.

Provider funnel visibility tech Keep tracking the missing intent events so Week 4 can report movement beyond audience growth.

ask Venture Spark

Pressure-test the liquidity path business Which path is most likely to turn the larger provider channel into real applications and completed shifts?

Review the CloudNurse verdict business Once tomorrow's outcome is known, help decide whether to double down, revise the ask, or move to the cold facility backup.

Pressure-test facility text-to-shift tech Is the facility LINE OA broadcast-text intake the right shortcut to reduce posting friction?

source trail

25 source files used

STATE.md
82,528 bytes - source body not rendered

AGENTS.md
4,748 bytes - source body not rendered

CLAUDE.md
7,741 bytes - source body not rendered