Week 3 · Week of 2026-06-24 · refreshed 2026-06-23T13:30:59+07:00

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.

next

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

Provider attention is now the test.

at a glance

vein can now show real shift demand before asking providers to register. The next test is converting soft-launch attention into role selections, shift views, applications, facility replies, and completed loops.

current status

Production-ready operating base tech The service stack is beyond MVP; this week's test is activation and intent, not whether the workflow exists.
Provider-side attention moved business The first public soft launch doubled the provider official account/OA count from 52 to 105 in a few hours.
Real shift demand can be shown first tech The product direction is anonymous role-first browsing: providers see relevant shifts before registration.
Open inventory can support launch business 100+ real shifts are now available as the basis for safe aggregate demand and provider-first browsing.
Current transaction proof remains one loop business The soft launch is top-of-funnel momentum; the durable proof still needs applications, accepted shifts, and completed loops.
CloudNurse meeting is ready business The next warm facility-access conversation has a sharper ask around permissioned facility introductions.

moved this week

Provider soft launch started business The first public provider-side post reached 6,400+ views; provider official account/OA count moved from 52 to 105 in a few hours.
Provider-first launch spine written tech The launch flow now shows real shifts before registration: choose role, browse shifts, then register when ready to apply.
Provider posting playbook ready business Channel order, captions, reply bank, stop rules, and content briefs are ready for controlled provider distribution.
Fresh shift inventory path scoped tech The team defined how cleaned, deduped shift inventory can feed the provider launch without exposing sensitive contact details.
Landing SEO Phase 0 shipped tech vein.md production now has the cleaner SEO base; the next step is demand-backed shift pages from safe aggregate data.
CloudNurse deck tightened business The 24 Jun meeting deck now centers the customer coverage gap, vein workflow proof, and a permissioned facility-introduction ask.
Provider funnel scoreboard started tech The analytics path now separates available launch counts from missing provider-app tracking events that still need instrumentation.

stuck

Soft launch is not transaction proof business Views, likes, and OA growth show message travel; they do not yet prove applications, accepted shifts, or completed work.
Provider funnel instrumentation tech Feed views, shift detail opens, apply clicks, and registration-started-from-apply still need provider-app tracking.
Facility self-serve tech The product is still not pulling facilities in by itself; founder-led and warm-access paths remain necessary.
Inventory safety and freshness tech Shift cards must stay fresh, deduped, role-clear, and contact-safe before broader provider distribution.
CloudNurse outcome pending business The 24 Jun meeting still needs to convert the prepared ask into real facility introductions.

next

Business
Run the 24 Jun CloudNurse ask business Ask for permissioned introductions to about three suitable facilities, without framing this as a software integration.
Convert provider attention into intent business Track role selections, shift views, detail opens, apply clicks, registration from apply, and provider questions.
Turn provider interest into facility conversations business When providers show intent around a shift, use that signal to approach facilities and confirm real demand.
Choose the first density wedge business Narrow the launch by role, geography, and facility type so the marketplace feels active in one focused lane.
Verify Search Console and submit sitemap business Complete the manual GSC step so the shipped SEO base can start being indexed.
Tech
Reverse-engineer Open Market import tech Document the exact import contract before building any real-time capture or parser output.
Build demand-backed SEO snapshot tech Generate safe aggregate shift-demand data for landing pages without exposing contacts or raw source mechanics.
Instrument missing provider funnel events tech Add feed, detail, apply, and registration-started tracking so Week 4 can report intent instead of attention.

ask Venture Spark

Pressure-test the provider-first pivot business Is showing real shifts before registration the right wedge, and what would make this look like proof next week?
Review the CloudNurse facility ask business Help sharpen the 24 Jun ask for permissioned facility introductions and the best first-facility profile.
Pick the Week 4 proof metric business Should the next update lead with role selections, shift views, apply clicks, facility replies, or completed shifts?
source trail

25 source files used

STATE.md
81,082 bytes - source body not rendered
AGENTS.md
4,748 bytes - source body not rendered
CLAUDE.md
7,741 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
04-Growth-Outreach/Product-Launch/2026-06-22-provider-first-launch-session.md
7,682 bytes - source body not rendered
04-Growth-Outreach/Product-Launch/2026-06-22-provider-launch-marketing-playbook.md
22,293 bytes - source body not rendered
04-Growth-Outreach/Product-Launch/2026-06-23-soft-launch-signal.md
2,191 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
43,682 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-landing/docs/superpowers/specs/2026-06-23-seo-demand-backed-shift-pages-design.md
7,493 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