Sent.
Your answers are with me. I'll be in touch within two to three days with a diagnostic, an Operating Layer architecture for your business, and a phased roadmap. A backup of what you sent has been downloaded to your computer.
Watch for an email from james.radina@gmail.com
James Sol Radina · AI + Systems Partner

AI as infrastructure,
not a feature.

I'm the AI and systems partner for founder-led companies in the $2M to $20M range. Whether you've built nothing yet or you have a stack of working prototypes that need to talk to each other, I help turn stick figures into smooth operating systems. Architecture, integration, and the polish that takes early builds to production.

0 yrs
Front-edge operator
0
Major shifts ridden
0
Layers of the system
3–4
Clients per year, by design
The System

The Operating Layer.

Five interconnected layers. Each one independently ownable. Together they form the operational nervous system of Bluewater Cruising as you've described it. You already have working prototypes inside several of these (FirstMate, CSMate, CS Co-pilot, Member Update Tool, the attribution rebuild). The work is connecting them, polishing them into production, giving them the UI and intelligence they deserve, and then evolving outward from there.

01 The Founder Layer FOR CHRIS 02 The Growth Layer KAURIE & SALES 03 The Team Layer KRISCHELLE 04 The Member Layer MEMBERS & CS 05 · THE SPINE The Data Layer Single source of truth across the stack THE OPERATING LAYER · v.06
01
The Founder Layer
For Chris
The CEO cockpit. Revenue, cohort pipeline, attribution truth, and decisions needing your input surfaced in one place. Strategic synthesis across Get Set To Sail, the brokerage, retreats, and content direction with Keith. Your highest-best use stays strategy and architecture, not chasing data across nine tools.
02
The Growth Layer
For Kaurie & sales
Voice-trained content production in your voice and Keith's. Cohort enrollment campaigns. Warm lead nurture between Compass Call and close. Keith's YouTube cross-promotion engine. Hyros, Meta, and Stripe reconciled so the data driving marketing decisions can actually be trusted.
03
The Team Layer
For Krischelle & the Bali team
Discord community ops. Content production coordination with Keith. Cohort enrollment workflows. Contractor flows for video shoots and brokerage support. Bilingual internal comms across the Bali team and the English-speaking distributed crew. Project state and decisions surfaced where the team actually works.
04
The Member Layer
For members & the CS team
The most active layer in your business. Member-facing: FirstMate evolved into in-program support during the 12-week cohort (boat-specific knowledge, budget guidance, passage planning), Discord presence, and offline cruising assistance two-plus years after purchase. CS-facing: polished CS Co-pilot and Member Update Tool giving full member context before every call, plus CSMate auto-firing onboarding sequences post-invoice. Smart enough to find alternative answers when prompts aren't phrased perfectly, instead of just failing.
05
The Data Layer
The spine underneath
Single source of truth across Hyros, Stripe, GHL, Meta, Discord, Airtable, Supabase, and the custom Claude Code AIOS you've already built. UTM consolidation so the same lead source is named the same way every time. Privacy compartmentalization so sensitive member conversations (financial, mental health, relationship) stay protected and never accidentally surface in marketing data or to staff who shouldn't see them.
See It In Motion

Each layer. What you'd actually see.

Most consultants describe their system. Here's what each layer could look like once it's live inside Bluewater Cruising. Tap a layer to explore. The Member Layer is interactive, trained on a sample of your actual program. Ask it anything a prospective student might ask.

Founder Layer · 01
Your morning briefing
7:42 AM LIVE
Revenue today
$0
2 couples enrolled overnight
Active pipeline
$0
23 couples in active conversation
Decisions pending
0
2 require your input
Today's strategic items
Synthesized overnight
Compass Call request. Mike & Jenna in Vancouver, planning a Pacific crossing in 18 months. High intent, asked three sharp questions in the form. Reply drafted in your voice, ready to send.
3 min read
Attribution flag. Hyros and Stripe disagree on yesterday's Cohort 14 launch revenue by $4,800. Data Layer flagged the discrepancy for review.
Needs decision
Discord moderation OK. Krischelle's weekly summary ready. Three contractor approvals queued from Keith's YouTube production team.
2 min skim
Today's calendar
Prep notes attached
09:00
Compass Call with Mike & JennaVancouver couple, Pacific crossing planning
Prep ready
11:00
Sales pipeline review with KaurieCohort 14 enrollment, two warm couples to nudge
Prep ready
14:30
Discord live session prep with KeithThursday Q&A topic: anchoring under load
Prep ready
Growth Layer · 02
Content production + attribution
Voice-trained · LIVE

Content queue Drafted in your voice

"Last week I watched a Cohort 13 couple anchor for the first time in 25-knot gusts off Catalina. Six months ago they thought a winch was a complicated piece of furniture. The program works because we don't pretend the ocean is forgiving..."
"Quick one. In Week 8 of last cohort, a participant asked me what I'd do if my autopilot failed offshore at night with my partner sleeping. The answer wasn't a checklist. It was a way of thinking we spend the program building..."
"5 anchoring mistakes that scare new cruisers. Keith's video script + intro tied back to the Compass Call landing page. Drove 47 calls booked in 18 hours."

Attribution truth Cohort 14 launch

Hyros
$0
Stripe
$0
Meta
$0
Reconciled. Variance reduced from 23% (Cohort 12 launch) to 2.6% (today). The remaining gap is Meta's view-through attribution from Keith's YouTube audience. Yours to keep, dismiss, or investigate.
Team Layer · 03
Operations coordination
EN · ID bilingual · LIVE

Active workstreams This week

Cohort 14 enrollment
Owner · Kaurie
Get Set To Sail · Q3 content
Owner · Keith
Discord community ops
Owner · Krischelle
Keith YouTube cross-promo
Owner · You

Bilingual comms Last 4 hrs

ID Krischelle · Bali ops
"Studio bookingan untuk Keith video shoot besok sudah dikonfirmasi. Saya butuh approval untuk pembayaran kontraktor."
Studio booking for Keith's video shoot tomorrow is confirmed. I need approval for the contractor payment.
EN Kaurie · Marketing
"Cohort 14 email sequence is ready for the Bali team to review the local market subject lines."
Rangkaian email Cohort 14 sudah siap untuk tim Bali meninjau subject line untuk pasar lokal.
ID Wayan · Admin Bali
"Invoice dari kontraktor video #7 untuk Keith YouTube edit. Sudah saya unggah ke dashboard."
Invoice from video contractor #7 for Keith's YouTube edit. Uploaded to the dashboard.
Member Layer · 04 · INTERACTIVE
AI concierge for your buyers
Try it · DEMO
B
Bluewater Cruising Concierge
Online · Trained on Get Set To Sail
DEMO
Hi, welcome to Bluewater Cruising. I can answer questions about Get Set To Sail (the 12-week program), the Compass Call booking process, our instructors, the Discord community, or really anything about what we do. What's on your mind?
What this would feel like for Bluewater members.

This demo is trained on a sample of your actual Get Set To Sail program structure, pricing, instructor backgrounds, and FAQs. In production, it would also know your live cohort calendar, alumni testimonials, and the full prospectus.

Try a question
NOTE A real Member Layer would integrate with your GHL CRM, hand off to Compass Call coordinators at the right moment, and respect every boundary you set about what stays internal.
Data Layer · 05 · THE SPINE
One source of truth
Reconciled · LIVE
Hyros
$0
Last 7 days
Stripe
$0
Last 7 days
Meta · attributed
$0
Last 7 days · view-through
Single source of truth
"What did we actually make this week?"
$0
Live event stream
Real time
How We Work

Three phases, shaped to where you are.

Some founders haven't started. Some have built working prototypes that need to talk to each other, get polished, and reach production. The arc respects both. Pricing is bespoke to scope and comes back with your proposal, two to three days after Discovery.

Phase 00

Diagnostic & Roadmap

Standalone deliverable, whether or not you've built anything yet. Full map of your current systems (the ones running and the ones being prototyped), the data flows, the attribution leaks, the workflow drift. Architecture proposal for what The Operating Layer would look like for your business. Sequenced roadmap with phased priorities, delivered as a Loom walkthrough, Figma diagram, and one-page executive summary.

Success marker: a roadmap you'd happily hand to any senior technical leader, including one that isn't me.
30 days
Fixed scope
Either party exits clean
Phase 01

Integration & Polish

For founders with existing building blocks (Discord bots, internal AI tools, custom dashboards, attribution work) that need to be connected, polished into production, and given proper UI/UX. Or for founders starting closer to zero and building from the architecture up. I lead the engagement; a vetted AI and systems builder ships in your stack. Component-by-component cutover, never a big-bang switch. Code in your GitHub from day one.

Success markers: stick figures turned into smooth operating systems. Tools that talk to each other. 30 to 60% reduction in daily tool-switching. Attribution variance reconciled. UI your team and your buyers actually want to use.
3 – 9 months
Shaped to scope
Monthly retainer
Phase 02

Embedded Partner

The AI and systems brain in the room, ongoing. Architecture decisions, execution drive-through, pattern-spotting, identifying problems before they bite. Nightly self-healing system audits. Evolution. The engagement runs without me being a single point of knowledge, but I stay close enough that the work compounds. Option to convert to full-time at any point if the right fit emerges.

Success marker: team operating from the cockpit daily, the system getting smarter on its own, and your highest-best use as founder is strategy and architecture, not implementation.
Ongoing
Reduced cadence
Long-term partner
Why Me

Six shifts. One pattern.

You've now seen what we'd build and how we'd work together. The natural next question is whether I'm the right person to build it with. Twenty years across six major shifts. The operators who win these moments aren't the ones who arrive after the playbook is written.

Shift 01
Real Estate
2002Southern California, early in the housing run
Shift 02
Internet Marketing
2005When SEO and email was being figured out
Shift 03
Mobile Apps
2010Very early, with an exit
Shift 04
CBD & Wellness Travel
2016Both industries at infancy
Shift 05
Crypto
2017Early through the formative cycles
Shift 06 · Now
Artificial Intelligence
2025–The infrastructure phase
The Posture

Most operators are treating AI as a productivity feature. A faster way to write captions. A better autocomplete. A fancy chatbot bolted onto a funnel.

That's not what wins this shift.

The companies that come out of this decade in dominant position will be the ones that treated AI like infrastructure. Built into the operating layer of the business. The thing the team runs from. The thing buyers experience. The thing decisions are made inside of.

James Sol Radina
James Sol Radina · Supporting Your Business In This AI Shift
The Discovery

Six questions. Ten minutes. Audio works beautifully.

This is where every engagement starts. Six big questions designed to surface what an exploratory call would normally pull out of you, except you can answer in your voice, edit anything before you send, and we save ourselves a meeting. Your answers come back as a diagnostic, a proposed Operating Layer architecture for your business, and a phased roadmap scoped to your timeline and budget. Two to three days from submission.

01
Audio over typing.
Click record, speak naturally, watch your words appear. Edit any transcription before submitting. Voice carries more than text can.
02
Cannot be lost.
Every keystroke autosaves to your browser locally and works fully offline. Close the tab, lose Wi-Fi, come back tomorrow. Nothing is lost.
03
You own everything.
Code in your GitHub from day one. Data in your accounts. Documentation transferred. No black box, no lock-in, no leash.
Begin Here

Your discovery.

Answer what you can, in whatever depth feels honest. Leave blanks where the answer is "I don't know yet." The blanks teach me as much as the answers do.

Saves continuously, fully offline. Your answers live locally in this browser, so closing the tab, walking away mid-session, or losing internet loses nothing. Come back any time on this same browser and pick up exactly where you left off.
0 / 6
Final Step

Ready when you are.

Hit send below. Your answers go straight to me, and a JSON backup downloads to your computer at the same time. You'll see a confirmation overlay when it's through.

What Happens Next

After you submit.

01
I read everything. Twice.

Once for the words, once for what isn't said. The blanks teach me as much as the answers.

02
Two to three days.

You receive a diagnostic summary, a proposed Operating Layer architecture for your business specifically, and a phased roadmap with costs and timeline.

03
A 60-minute call to walk through it.

I answer questions, refine anything that needs to shift, and we lock the option and timeline together.

04
If we're a fit, we begin in as little as two weeks.

Phase 00 Diagnostic kicks off. The engineer is named, introduced, and locked. From there, the work moves.

A note on capacity. I take on a maximum of three to four major clients per year at this depth. That keeps the work close and the attention undivided. If we're not the right fit for an engagement this round, you have my word: I'll still give you something useful from the discovery, and if I know someone better positioned to help, I'll make the introduction. Your time investment in this is honoured either way.
Common Questions

Questions that come up.

The ones founders ask before they ask. Answered honestly, before the call.

Why isn't this just "AI consulting"?
Because consulting ends at the recommendation; this ends at the production system. Most AI consultants give you a deck and a Slack channel. I'm the AI and systems brain on your team, designing the architecture and driving execution forward, with a vetted builder shipping code in your repos. If you've already built prototypes (Discord bots, internal AI tools, custom dashboards), the work is connecting and polishing them. If you're starting closer to zero, the work is building from architecture up. Either way the deliverable is a system your team uses on Monday morning, not a roadmap you have to staff.
Why not just hire a full-time Head of AI?
For most $2M to $20M founder-led companies, the full-time Head of AI hire takes 60 to 90 days to ramp, costs $146K to $273K in base comp alone, and they're learning your business while you're paying them. A fractional engagement with a vetted engineering bench delivers production code by month three at materially lower cost. If we get to month nine and full-time is the right next move, we can convert the engineer (and the role) at that point with full context already in place.
Who builds the actual code? Do I need a traditional software engineer?
I'm the architect; a vetted AI and systems builder is the hands. For most engagements over the next year, you don't need a traditional software engineer. You need someone who can vibe code in Claude Code, thinks like a builder, pushes back on bad architecture, and drives execution forward. I have a small bench of 2 to 3 of these people. Before Phase 01 begins, the builder is named, introduced to you on a video call, and locked exclusively to your engagement for that phase. If you'd prefer a different builder mid-engagement, that's a 30-day swap with no penalty. Occasional contract hours from a traditional software engineer may be needed for security or privacy audits; that's planned for and budgeted separately.
What happens if I want to part ways mid-engagement?
30-day written notice past Phase 00. No minimum lockup, no early-termination penalties. Everything built up to that point lives in your GitHub, fully documented, with an engineer profile that's hireable. You leave with a working system and zero black box. The whole engagement is structured so the off-ramp doesn't punish you for taking it.
Will this disrupt what we already have running?
No. Your current GHL funnel, Hyros tracking, Discord, Stripe, Meta campaigns keep running untouched during the build. The Operating Layer is built in parallel and switched over component by component once each piece is verified live in production. Your team keeps their daily tools until each replacement is proven. Never a big-bang cutover.
Why don't you publish client names?
Both current engagements involve sensitive operational data, internal margins, and contractor relationships that the founders prefer to keep private. I won't break that on a website. If you'd like to talk to either of them, I'll arrange a warm introduction under mutual NDA. Same answer I'd give them about you if you were a future client.
What if my business is mission-driven or wellness-focused? Will the work respect that?
I work specifically with founders building this way. Wellness travel and regenerative business were two of the six shifts I came up through, not theory I learned to sell into. The Operating Layer is designed to amplify the values you've already built around, not flatten them. Voice training preserves your cadence. The Member Layer doesn't sound like a chatbot. Boundaries about what stays human are explicit in every scope.
Where does pricing come in?
In the proposal that comes back to you two to three days after the Discovery. Every engagement is bespoke to scope, which is why a fixed price on this page would be either misleading or wrong. After you submit the Discovery, you receive a proposed architecture, a phased roadmap, and pricing shaped to where you actually are. For context: this work is structured to pay for itself inside year one through reduced operating cost (fewer tools, fewer hours lost to context-switching, less revenue leaking through bad attribution), unlocked efficiency (team focused on the work that compounds instead of the work that maintains), and surfaced revenue the current scaffolding is leaking out the back. The larger return is becoming an AI-equipped company at a moment most of your competitors are still figuring out what that means.
The Operating Layer
"The operators who win these moments aren't the ones who arrive after the playbook is written. They're the ones who write it."
James Sol Radina · Bali · 2026
Saved · just now