Founder Playbook · The Bootstrapped Founder
7 tactics from Arvid Kahl
Risks and Rewards of Building on OpenAI
Watch the full episode“if your business success is predicated on making it slightly cheaper to access what open AI offers or slightly easier you're in trouble they can and do change pricing and their UI and access restrictions and interfaces at any point”
Stop being a wrapper — be a focused solution
If your value prop is "slightly cheaper / slightly easier access to GPT," the platform will close that gap and your business evaporates. The defensible play is the opposite: pick a specific user (estate planner, bridesmaid speech writer, podcast publisher) with a specific workflow, and use the model as one ingredient inside a tailored end-to-end product. Wrappers compete with the platform; focused solutions compete with the customer's current way of doing the job.
“when customers find a product that reliably solves their specific problem in itself a very specific way well they don't jump ship towards a more generic implementation easily particularly when your customer are not technical people”
Customer inertia beats technical equivalence
Non-technical buyers do not churn from a tool that already solves their exact problem in exchange for a slightly cheaper, slightly more generic alternative — even when the generic option is technically superior. The minute they paid you, they bought the right to stop thinking about it. Optimize for keeping the problem solved on your customer's terms; do not assume rational price-shopping behavior.
“look at how many specialist hosting providers exist for web apps right if it was just about saving the most money every single person would host on AWS but in reality people have different preferences they want more than a generic platform”
Niche solutions exist because cheap-and-generic does not fit most people
Every layer of infrastructure has both an AWS-style raw platform and a thriving ecosystem of specialist tools (Vercel, Render, Fly, Railway) built on top of it. AWS hasn't "killed" the specialists — it enables them. The same logic applies to OpenAI: there is room for hundreds of specialist tools sitting on top of one base model because users buy fit, not raw access.
“no more spending time trying to manage embeddings and providing context from these embeddings we spend a ton of time building this in house now everything is about to become a simple parameter in an API call we can delete a lot of our custom code”
Platform feature drops often help you — they delete your custom code
When the underlying platform ships the feature you were duct-taping together, panic is the default reaction — but Banua at SciSpace welcomed OpenAI shipping native embeddings/retrieval because it deleted months of custom infrastructure his team was maintaining. Reframe platform releases: each one collapses a layer of your engineering cost, freeing you to invest that capacity in features the platform will never build.
“for every customer who makes such a speech you can add a new record into your database over time you can then use more AI internally to learn what good speeches are made of... you may not control the means of production you don't have the AI it's not yours but you own the ingredients the recipe and the finished product”
Your real moat is data + audience, not the model
You don't own the model — but you own everything around it: the inputs, the prompts, the output ratings, the customer communications, the audience around the problem. That data set + relationship gets richer every customer; the model on its own does not. Track what you uniquely accumulate that the platform never sees: corrections, preferences, segment outcomes. That is the asset that survives any platform pivot.
“for those founders with a low risk tolerance well consider generative AI tooling as a feature maybe not the core of your product... you can also diversify open AI isn't the only platform... if you have a high appetite for risk as a business owner you can build products using open AI tools and then try to monetize them very quickly”
Match your platform dependency to your risk tolerance — pick one of three tiers
Three explicit tiers to choose from with eyes open. (1) Low risk: AI as a feature inside a product that works without it — your business survives any platform change. (2) Medium risk: abstract over multiple providers, possibly self-hostable, so swapping providers is a config change. (3) High risk: go all-in on OpenAI and race to monetize while the wave is breaking. None of these is wrong — but mismatching tier and risk appetite is.
“industry specific data Transformations or workflow Integrations that are really nitty-gritty it's not what open AI cares about but you can do this and your customers will thank you for it”
Ship the nitty-gritty workflow features the platform won't bother building
OpenAI's core business is training and renting a general model — they have no economic incentive to build bulk PDF import, white-label embeds, vertical workflows, role-specific UIs, or industry-specific data transforms. Those are exactly the features that turn a wrapper into a real product. Build the integration ugly-edges your specific customer hates doing themselves — that's the moat the platform is structurally unwilling to fight you for.