01 / 09
Kahlil Corazo → Symph — A Counter-Proposal

A client who becomes
your best case study.

Dave, your proposal was beautifully built — and the audiobook app is exactly right. But there's a bigger opportunity here than a single project. What if this engagement becomes the prototype for a service line you don't yet offer: vibe-coding mentorship for entrepreneurs who want to build, not just buy?

From Kahlil Corazo
To Dave, Albert, and the Symph team
Date April 2026

There are thousands of entrepreneurs who want to build with AI but don't know how to work with a dev team. They need a trusted technical partner who can mentor them into capability. Symph can be that — and I'm the first client to help you figure out how.

— The opportunity in plain language
A bigger picture

The proposal was right.
The frame was too small.

The audiobook app is real and I want it built. Your stack, your timeline, your AI-agentic pipeline — I accept all of that. But treating this as a standard client engagement leaves value on the table for both of us.

What I'm proposing adds one layer to what you already planned: make me a co-builder, not just a buyer. That changes the revenue model, the relationship, and what Symph can do with the story afterward.

✓ What works, unchanged
The audiobook app. React Native + Expo. AI-agentic build timeline. The design quality of your proposal shows you understand craft — that's exactly why I came to you.
+ What this proposal adds
A mentorship layer: I co-build under your guidance, not just receive delivery. This takes modestly more of your time — but unlocks a recurring relationship, a case study, and a new service line.
✓ What doesn't change for Symph
You still architect. You still lead. You still set the quality bar. The difference is I'm learning from you in the process — and paying for that privilege.
Context you should know

I'm not a
typical author-client.

Fifteen years running a digital marketing company. Published academic work. Frankfurt Book Fair presenter. And three weeks ago, I shipped my first vibe-coded app solo — an AI-powered literary analysis tool — using Claude and Cloudflare Pages.

I understand enough to be dangerous. I need a team that will help me be useful instead.

The app exists. The curiosity is real.
✍️
Writer & Public Intellectual
Published in Contagion: Journal of Violence, Mimesis, and Culture. Author of Rajah Versus Conquistador. Substack: Explorations.
🏢
15 Years as an Entrepreneur
Runs a digital marketing firm with a Dutch partnership (SUM Digital). Deep familiarity with client-vendor dynamics — from both sides of the table.
🛠️
Already Vibe-Coding
Shipped writerdna.explorations.ph three weeks ago. Claude + Cloudflare Pages. A real, working, deployed app — built alone, from scratch.
writerdna.explorations.ph →
🌐
Early Adopter, Not a Skeptic
I used AI tools to compress 5 years of novel-writing into 15 months. I'm not learning about AI — I'm already inside it. I need to go deeper.
The operating model

Symph owns production.
I build capability in parallel.

My real goal is not just to ship one app. It is to become operational in a world where intelligence is on tap, without yet knowing which opportunities will matter most. That requires a working arrangement where I can prototype fast, learn directly from the code, and still keep commercial production safe.

01
Sandbox first
I want direct access to the codebase, but write access only to the sandbox for commercial apps like RVC. I prototype what I want there. That is where I learn, test ideas, and move quickly.
02
Production stays with Symph
Symph owns the production code. My internal programmers — part-time interns and fresh grads who are AI-vibecoding natives but trained programmers — submit proposed changes. Symph QAs, approves, and controls what reaches production.
03
Aligned incentives
I do not want a structure that incentivizes Symph to limit scope. I want freedom to keep growing the RVC app and to build other tools too — some internal, like thesis data analysis, and some commercial. The relationship should expand with opportunity, not choke it.
Project One — Rajah Versus Conquistador

The app is real.
But the scope should be open-ended.

Your technical direction was right: React Native + Expo, Android first, freemium audiobook. But I already know this product wants to grow beyond the currently documented scope, and I do not want the engagement designed around keeping it small.

Some additions should be part of v1. Others belong in the first expansion wave after launch. And I will likely think of more once the app is alive in the market.

Build the first version, then keep compounding
V1
Read while listening — ebook and audiobook synchronized in one experience
V1
Curriculum request flow — let teachers or schools request integration into a subject or reading list
Post-launch
In-app purchases for RVC-related materials and other books in my catalog
Post-launch
RVC bot so readers can ask questions about the book inside the app
Working style
Prototype in sandbox, harden in production — I explore; Symph decides what is ready to ship
Principle
The app is not a fixed deliverable. It is the first node in a growing product family around RVC, my books, and future tools.
Why this is good for you

What Symph
gets from this.

I'm not asking you to teach for free. I'm offering you something more interesting: a prototype client for a revenue stream you don't have yet.

There are thousands of entrepreneurs — business owners, writers, researchers, executives — who want to build with AI but don't know how to work with a dev team. They need someone to mentor them into capability, not just deliver to them. I am that customer. And if this works with me, you'll know how to sell it to others.

I'm your proof of concept
🧪
A New Revenue Stream — Prototyped
"Vibe-coding mentorship for entrepreneurs" is an untapped service category. I'm the first client. Work out the format, the pricing, the structure — with someone who won't punish you for getting it wrong the first time.
📣
A Champion, Not Just a Testimonial
I write publicly about AI and entrepreneurship to a real audience. I run a young executives organization. I speak at events. When this works, I don't give you a star rating — I send you clients and tell the story properly.
🧠
A Thinking Partner on the Product Side
I've spent 15 years understanding what non-technical people actually want from tech. That perspective is useful when you're designing a mentorship offering — I can tell you what the market needs to hear.
🔁
A Long Pipeline of Real Projects
RVC app, after-school academy platform, research tools, more books. I'm not a single-sprint client. The relationship grows as my skills grow.
Honest answers

The objections
are reasonable.

What I am asking for is unusual. So the tone here should not be defensive or salesy. These are legitimate risks. My point is that there is a clean operating model that contains them.

⚡ “This could consume too much senior time”
Then price that time explicitly. I am not asking for free mentorship. The retainer should reflect review time, QA time, and occasional rescue time.
⚡ “You might slow down the sprint”
That is exactly why sandbox and production are separated. I experiment in sandbox. Symph protects the production roadmap.
⚡ “More features will keep moving the goalposts”
Yes, the product will grow. That is a feature, not a bug. The answer is not artificial scope-constraining; it is clear prioritization between v1, post-launch, and future products.
⚡ “This is not a standard productized service”
Correct. It is a bespoke operating relationship for an AI-native client. If it works, Symph gains a replicable model for other founders who want capability, not just delivery.
Beyond the audiobook app

The long game
is optionality.

My long-term goal is to operate effectively in a new environment where intelligence is on tap, without pretending I already know which opportunities will matter. The point is to build capability, process, and trust now so that future opportunities are easier to seize.

That is why I expect to hire part-time interns and fresh grads who are native to AI-assisted coding but still grounded in programming. Over time, I want an internal layer that can prototype and extend ideas — while Symph remains the trusted production gate for commercial products.

Capability first. Opportunities follow.
Now
RVC App + Working Rhythm
Launch the first commercial product and establish the sandbox-production operating model.
Next
Internal Tools
Use the same model for internal systems, including my thesis data analysis and research workflows.
Then
More Commercial Apps
Spin out new products from books, educational ideas, or market opportunities we cannot yet fully specify.
Outcome
Symph as Technical Sovereign
My internal team becomes faster at prototyping; Symph remains the partner trusted to QA, approve, and ship what matters commercially.
Why Symph, despite cheaper options

There are cheaper ways
to build this.

I know there are lower-cost options, including Fiverr-style execution. I am choosing Symph anyway because the point is not to get the cheapest app shipped. The point is to work with a team I trust to help set up the right technical rhythm, product judgment, and production discipline.

This is not only about one app. It is about establishing a working model I can keep using as I build more internal and commercial products in an AI-native environment.

Author Kahlil Corazo
Substack explorations.ph
First app writerdna.explorations.ph
Location Davao City, PH