Lonely Pine AI Collaborator Brief
What we build, and where you'd start

One studio. Eight production systems. Built with AI, end to end.

A walkthrough of Lonely Pine AI: the live client systems, the architecture underneath them, and the project we'd bring you onto first.

Prepared for
Nozomi
Prepared by
Nalu, Lonely Pine AI
Date
July 2026
First project
Halehaku Maui
01 / What Lonely Pine is

AI handles transactions so humans can handle interactions.

Lonely Pine AI is a founder-led studio based in Tokyo, serving clients in Hawaii and beyond. After a decade at a Fortune 10 company, Nalu left in June 2025 to build AI systems for real operators: restaurants, vacation rental managers, boutique resorts, painting contractors. Not demos, not decks. Production systems that answer phones, write orders, and run back offices every day.

4
Service lines
Voice agents, workflow automation, intelligence dashboards, and fractional Chief AI Officer engagements.
24/7
Live voice coverage
AI agents on real phone lines: food ordering, guest services, lead capture, outbound follow-up.
1 + AI
The whole team
One founder, AI-augmented from design to deploy. That is the operating thesis, and it works.
02 / Shipped and live

Real clients, real production.

Every system below is deployed and in use today. The architecture line under each card is the part you asked about.

Restaurant · 3 locations

Sparky's Food Co.

Hoku, an AI phone agent that takes food orders on the main line, prices them from the live Square catalog, writes real orders into Square, and texts payment links. Plus an order tracker that reconciles phone revenue on scheduled jobs, and a native rewards app now in proposal.

StackVapi voice · Cloudflare Workers (TypeScript) · Square API · cron reconciliation · Twilio SMS
Painting contractor · Fractional CAO

Equipped Painting

Steward, a Claude-powered operations agent the whole team uses: pipeline intelligence from their CRM, call attribution, weekly scorecards into Slack, a tagged knowledge corpus with semantic search, and a console the owners live in. Delivered inside a fractional Chief AI Officer engagement.

StackClaude API · Workers + D1 + Vectorize · DripJobs, CallRail, CompanyCam · Slack · 239-test suite
Beach resort · Voice + ops

Kamaole Beach Club

Malia, a guest-facing voice agent that handles arrival questions and weekly check-in logistics, plus an operations dashboard behind magic-link auth. Now building their reservation-system MVP as the first quarter of a fractional CAO engagement.

StackVapi voice · dedicated Worker + D1 · magic-link auth · weekly config overrides · Pages frontend
Vacation rentals · 72 units

DMV Maui

Lani, a voice agent that quotes live availability sourced from the real booking site, refreshed by a pre-warming cron across all 72 units. Around it: automated weekly email newsletters, a monthly reporting suite, and a social content system.

StackVapi voice · live-scraped availability + KV cache · Mailchimp API · scheduled report generation
Hospitality group · Document AI

DMI / Blu

Blu, a document-intelligence assistant for a hospitality development group: ingestion pipelines for their file corpus, DOCX round-trip editing, threaded conversations, and locked-template daily and monthly reports on scheduled crons.

StackClaude API · Workers ingestion + Vectorize · DOCX generation · cron-driven reporting · email distro
Resort condo · Ops dashboard

Maui Eldorado

Operations dashboard on a real database: guest check-in forms routed straight into D1, competitor-listing suppression handled by a scheduled job, and an automated monthly owner report.

StackPages + D1 · form-to-database routing · suppression cron · automated monthly reporting
Tokyo church · Pro bono · Mobile

Franciscan Chapel Center

A full native mobile app shipped to both the App Store and Google Play: schedules, announcements, push-ready architecture, a beta program with 26 testers, and a feedback pipeline writing into a database, plus admin dashboards.

StackReact Native + Expo · EAS builds · both app stores · D1 feedback pipeline · Pages admin
Internal · The cockpit

LP Command Center

The studio's own operating cockpit: daily pulse across every client system, checklists, and status boards, all behind zero-trust auth. The same patterns clients get, pointed inward.

StackDedicated Worker + Pages · Cloudflare Access (zero-trust SSO) · cross-system status aggregation

Also live: hawaiicustomtreasures.com, a pro bono small-business site, and Wayfinder AI, the studio's own newsletter and funnel.

03 / Under the hood

One architecture, many clients.

Everything runs on the same layered pattern. A client engagement is mostly configuration and integration on top of proven plumbing, which is why one person can run eight production systems.

Voice layer
The front door

Inbound and outbound phone agents with per-client prompts, tools, and guardrails. Each agent calls back into our backends for live data mid-conversation.

VapiRetellTwilio numbersTTS pronunciation rulessilence + idle handling
Agent intelligence
The brain

Claude powers the reasoning: conversation agents, document analysis, report drafting, and semantic search over client knowledge corpora with sensitivity tagging.

Claude APItool callingVectorize embeddingsRAG over client corpora
Backend layer
The plumbing

Production TypeScript on Cloudflare Workers. Started as one shared Worker, now peeled into dedicated per-client Workers with audited auth gates, scheduled crons, and a fail-loud rule for anything automated: broken reports page us, they never silently skip.

Cloudflare WorkersTypeScriptcron triggersper-client isolationautomated test runner
Data layer
The memory

Serverless SQL for operational data, KV for config and caching, vector storage for semantic search. Every client gets isolated data with ownership checks.

D1 (SQLite)KVVectorizeper-client databases
Integrations
The nervous system

The systems clients already run, wired in both directions: point of sale, CRM, call tracking, email, payments, chat.

SquareDripJobsCallRailCompanyCamMailchimpSlackGoogle APIsStripeTwilio
Frontends + auth
The surfaces

Dashboards, consoles, and client apps on Cloudflare Pages, gated by zero-trust access or magic-link auth. Native mobile via React Native and Expo when the product calls for it.

Cloudflare PagesCloudflare Accessmagic-link authReact Native + Expo
Build system
The multiplier

The entire studio is built and operated through Claude Code: design, implementation, tests, deploys, and reporting run as deep AI-collaborative sessions with hard, mechanically enforced quality rules. This is the part most shops have not figured out yet.

Claude Codeenforced brand + content rulessession continuity systemCOE database
Why this matters: none of these clients could justify a traditional dev team. The stack above keeps marginal cost near zero, so a solo studio can ship and operate systems that normally take a department.
04 / In flight right now

What's being built behind the scenes.

01Kamaole Beach Club reservation system. A ground-up reservation MVP for a timeshare resort, targeted for early September. Availability, booking, and staff tooling on the Workers + D1 stack.
02Equipped Steward v-next. A control interface for their sales voice agent, a finance tab, stale-lead automation, and live production-sheet sync. The agent grows into the company's operating system.
03Sparky's rewards app. Native loyalty app on top of the existing Square integration: order, earn points in store and online, redeem. Proposal is live with the owners now.
04Wayfinder AI. The studio's own newsletter and audience funnel, relaunching with a publishing pipeline.
05Halehaku Maui. The newest engagement, kicking off this week. Detail on the next screen, because this is where you would come in.
05 / Where you'd start

Halehaku Maui. Day one is tomorrow.

A single-page website build for Halehaku Maui, a Maui store run by Felix Vandyke. Small scope on purpose: it is the full arc of a client engagement, design through launch, compressed into about two weeks. Ideal first project to work end to end together.

1
Page, done right
Responsive single-page site: story, services, work gallery, contact form, click-to-call. Fast and hard-edged.
Tue
First milestone
Design mockup options go to Felix and family on Tuesday. They pick a direction, we build it out.
~10
Business days to launch
Intake, copy, design, one revision round, then DNS and launch on the client's own domain.
Tomorrow
Kickoff · intake, photo gathering, design direction exploration
Tuesday
Design mockups to the client · two or three directions to choose from
This week
Copywriting + build · chosen direction becomes a real page
Next week
Revision round · client feedback folded in
~2 weeks out
Launch · client domain, on-page SEO, handoff
Your seat: you join from the beginning phases, as much as you want to take on. Design exploration, build, deploy pipeline, launch checklist. You see how a Lonely Pine engagement actually runs, on a project where the whole thing fits in your head.
06 / How we'd work

Start free, ship real, grow from there.

01Pro bono to start, real credit always. Everything you ship is production work with your name on it. A portfolio of live systems, not tutorial projects.
02Learn the AI-augmented workflow. You work the way the studio works: Claude-driven builds, fast iterations, mechanically enforced quality rules. The skill you are actually here to build.
03Async and flexible around your day job. Scoped pieces you can pick up on your own schedule. No standing meetings.
04A real path to paid side work. As fit develops, paid project work is on the table. If this becomes your way out of the current job, that is a good outcome for both of us.

Let's build something that's live by next week.

Lonely Pine AI · JDKC Ventures LLC · nalu@lonelypine.ai