Breakdown: Kris Chase, PeptIQ Founder, on App SEO Growth to $115K
How Kris Chase validated PeptIQ, shipped an MVP in about a week, and turned patient SEO and an embedded calculator into a subscription app with $115K+ in reported revenue.
PeptIQ’s app SEO growth came from answering specific questions, adding a useful calculator, and giving searchers a reason to create an account. In a Starter Story interview with hosts Pat and Gus, founder Kris Chase reported more than $115,000 in revenue that year and roughly $14,000 in monthly recurring revenue while continuing his fractional CTO work.
The interesting part is not a supposedly untouched app category. PeptIQ entered a competitive market, then connected educational search traffic to a subscription product. The answers below paraphrase Chase’s account, with operator commentary separated from his claims.
TL;DR
- Demand came before development: Chase researched social conversations, Google search trends, successful competitors, and app reviews.
- The MVP took about one week: Chase used Vibecode, backed by approximately 25 years of programming experience.
- SEO needed patience: Chase reported waiting six or seven months before meaningful benefits appeared.
- Content led into a product workflow: An article included a calculator whose results could be saved into PeptIQ through account creation.
- The numbers need distinct labels: Revenue, monthly recurring revenue, search clicks, and profit are not interchangeable.
PeptIQ business snapshot
- Founder: Kris Chase, software engineer and fractional CTO.
- Business: PeptIQ, a peptide tracking subscription app.
- Reported revenue: More than $115,000 during the year discussed.
- Recurring revenue: Approximately $14,000 reported, with a RevenueCat dashboard displaying $14,539 MRR.
- MVP development: About one week.
- Pricing described: About $30 monthly or $130 annually, using a hard paywall.
- Main growth channel: Google organic search, which Chase attributed roughly 70% of clicks and revenue to.
- Key tools: Vibecode, Expo, React Native, TypeScript, Supabase, RevenueCat, Vercel, PostHog, and Sentry.
What did Chase validate before building PeptIQ?
Why enter a market that already had competing apps?
Chase treated successful competitors as evidence of demand, not an automatic reason to leave. Existing GLP-1 tracking apps suggested that people wanted help managing this category of information.
His proposed difference was broader coverage. While other products focused specifically on GLP-1s, Chase believed other peptides represented an underserved opportunity.
That conclusion came from several signals:
- His own interest in finding the information.
- Discussions across Reddit, Instagram, and TikTok.
- A sharp increase in Google search interest.
- Existing apps demonstrating demand for related tracking workflows.
Chase also recommended reading competitor reviews and Reddit discussions to understand what already worked and where users wanted something different. Competition supplied research material. It did not supply a guarantee.
What would a practical validation checklist look like?
Chase’s research can be turned into a short checklist: establish demand, identify an underserved need, and connect that need to a specific product difference.
- Find repeated questions. Look for the same problem appearing across relevant community discussions.
- Check search interest. Use Google search trends to investigate whether attention is increasing.
- Inspect existing products. Identify the workflows competitors already serve.
- Read the complaints. Review app feedback and Reddit discussions for missing functionality.
- State the difference clearly. PeptIQ’s angle was broader peptide coverage rather than another narrowly focused GLP-1 tracker.
Roger’s take: I would steal the research sequence, not the category. “There are competitors” is incomplete analysis. The useful question is whether a specific group still has a specific problem those competitors handle poorly.
Was Chase starting from zero?
No. PeptIQ was Chase’s first app built for himself, but he described approximately 25 years of programming experience.
His fractional CTO work involved overseas engineering teams across web, mobile, QA, IT, and DevOps. He also reported building a MySpace-era business that generated about $40,000 monthly while he was in high school.
That background matters when interpreting the one-week MVP. A first personal app is not the same thing as a first encounter with software development.
How does PeptIQ make money?
What does the subscription product actually do?
PeptIQ combines peptide tracking with schedules, tools, educational resources, and community features. Chase described pricing of approximately $30 per month or $130 per year behind a hard paywall.
The product features he outlined included:
- Upcoming schedules and previous entries.
- An in-app community.
- A reconstitution calculator.
- Blood work uploads and journaling.
- A medication interaction checking feature.
- Educational guides.
- An AI question-answering feature using account context.
Chase said the AI feature could incorporate a user’s protocol, frequency, missed doses, Apple Health information, and blood work. That is a description of the feature, not evidence of clinical accuracy or improved health outcomes.
Which business numbers have supporting dashboard evidence?
The RevenueCat dashboard displayed $14,539 in MRR, 1,413 active subscriptions, 70 active trials, and $22,081 in revenue over the preceding 28 days. Chase separately reported crossing $115,000 in revenue during the year.
Those figures describe different things. The $22,081 revenue figure should not be relabeled as monthly recurring revenue, and neither figure establishes profit.
The interview did not provide a complete expense breakdown, churn analysis, or retention cohorts. It also did not establish the exact acquisition path for PeptIQ’s first paying customers. The strongest documented acquisition explanation concerns the later SEO channel.
How did PeptIQ’s app SEO growth strategy work?
Why did Chase prioritize Google rather than paid acquisition?
Chase built the marketing website around search early because he expected SEO to take time. The case describes growth without spending on paid ads or influencers, with Chase attributing roughly 70% of clicks and revenue to Google.
He reported that the primary paying and downloading audience was 45 to 55 years old. His reasoning was that this audience still used Google to find answers, making search a relevant distribution channel.
That is an audience-specific explanation, not proof that every demographic behaves the same way. The useful principle is to investigate where potential customers already seek help.
How long did SEO take to produce results?
Chase said meaningful SEO benefits took roughly six or seven months after a January launch. The search performance chart showed a long, relatively quiet period before a substantial increase.
Google Search Console displayed approximately 590,000 clicks over the selected 12-month period. That supports the scale of search traffic, but clicks should not be treated as unique visitors or paying customers.
Roger’s take: The boring stretch is part of the strategy. I would not use a seven-day traffic report to judge a channel that took Chase about half a year to develop.
What content brought relevant people to the website?
Chase focused on questions people repeatedly asked about peptides. One example addressed peptide reconstitution, a topic closely connected to PeptIQ’s calculator.
He described a mixed production approach: writing articles himself, using AI for a substantial share, and hiring writers. He did not provide publishing frequency, article count, writing costs, or a detailed editorial review process.
The supported lesson is therefore not “publish a certain number of AI articles.” It is to find recurring questions in a relevant community and answer them in a way that connects to the product.
How did an article become an account creation opportunity?
PeptIQ embedded a calculator into the educational article, then offered a way to save the entered information into the app. The content answered a question; the tool helped with the next task.
The path Chase described was straightforward:
- A person searches for help with a specific question.
- The article explains the topic.
- The person enters information into the embedded calculator.
- A save action leads into account creation.
- The information can then be saved into PeptIQ.
This is the most transferable mechanism in the case. The article and app serve adjacent stages of the same task, rather than asking an unrelated reader to download an app on faith.
No article-to-account or account-to-paid conversion rate was disclosed. The workflow is visible; its individual contribution to revenue remains unquantified.
What would the SEO implementation checklist include?
Which technical basics did Chase recommend?
Chase emphasized organized information, fast-loading pages, schema markup, semantic tagging, and working links. He presented these as foundational website requirements alongside useful content.
- Organize content clearly: Make the information understandable and navigable.
- Keep pages fast: Avoid treating loading performance as an afterthought.
- Use appropriate schema: Structure the page’s information explicitly.
- Use semantic HTML: Give headings and page elements their proper roles.
- Fix broken links: Remove avoidable obstacles for people and crawlers.
Chase named Semrush and Ahrefs for auditing a website and researching competitors. His suggested questions were practical: which competitor pages attract traffic, and which terms do those pages rank for?
Should an app’s marketing website target only Google?
Chase also recommended submitting the website’s sitemap to Bing. He referenced Bing’s relationship with OpenAI as a reason not to ignore that search ecosystem.
The practical action is sitemap submission, not an assumption that indexing guarantees inclusion in AI-generated answers. No separate Bing traffic or revenue result was supplied.
What tools did Chase use to build PeptIQ?
How did the one-week MVP come together?
Chase said Vibecode helped him turn the idea into a working app in about one week. The supporting stack covered mobile development, backend services, subscriptions, hosting, and monitoring.
- Expo and React Native: Mobile app development.
- TypeScript: Application language.
- Supabase: Database and authentication.
- RevenueCat: Subscription infrastructure and reporting.
- Vercel: Marketing website hosting.
- PostHog: Analytics.
- Sentry: Crash reporting and analysis.
No total startup cost was stated. Nor did Chase say every feature demonstrated in PeptIQ existed in the initial one-week version. The MVP timeline should not be stretched into a claim that the entire current product took seven days.
Roger’s Take: what is actually replicable?
What should a solo builder copy, and where is the hype?
The replicable part is the connection between demonstrated demand, a differentiated product, and useful search content. The reported revenue is an outcome from Chase’s business, not a forecast for another builder.
I would copy three things: researching repeated questions before building, starting the marketing website early, and designing one article around a task the app can continue.
I am more skeptical of the easy interpretations:
- “AI made experience irrelevant.” Chase brought decades of engineering experience.
- “SEO was free.” There was no paid acquisition bill described, but content work, hired writers, and infrastructure still existed.
- “Traffic proves profitability.” The case does not disclose enough costs to calculate profit.
- “A crowded market guarantees demand for another app.” Chase still needed a specific difference.
- “The calculator explains all the revenue.” Its conversion contribution was not isolated.
I would also separate the growth lesson from the health category. An app feature description does not establish the safety or accuracy of medication guidance or AI-generated answers.
What could a builder test this week?
A small test can reproduce the structure without trying to reproduce PeptIQ’s entire feature set. The goal is one useful path from a real question to a product action.
- Choose one repeated question from relevant Reddit discussions or competitor reviews.
- Check search demand and inspect the pages already answering it.
- Draft a focused answer rather than a broad category overview.
- Identify the next task the reader needs to complete.
- Prototype one tool that helps with that task and connects naturally to the app.
- Check technical foundations and submit the sitemap to Google and Bing.
For PeptIQ’s app SEO growth, the central lesson is simple: useful information became more valuable when people could act on it and retain the result.
Next action: Select one recurring customer question today and sketch the shortest path from its answer to a useful in-app action.
Source: This App Made Over $100K in 1 Year by Starter Story.
🧰 Build This Stack
The first three are tools Chase named in his own stack; the last two are solid alternatives, not tools he said he used.
- Vibecode for turning the idea into a working MVP — Chase’s own pick, alongside Expo and React Native
- Supabase for the database and authentication — part of Chase’s stack
- RevenueCat for subscriptions and the hard paywall — the dashboard behind PeptIQ’s reported MRR
- Framer for your app landing page and SEO content — a solid alternative to the Vercel-hosted marketing site Chase used
- Lovable as an AI app builder — a solid alternative for prototyping a web tool like PeptIQ’s embedded calculator without much code
Some tools above may be affiliate links — we only list tools that fit the build.
FAQ
How much revenue did PeptIQ generate?
Chase reported more than $115,000 in revenue during the year discussed. A RevenueCat dashboard displayed $14,539 in monthly recurring revenue and $22,081 in revenue over the preceding 28 days.
How long did PeptIQ’s SEO take to work?
Chase reported waiting approximately six or seven months for meaningful SEO benefits. Google Search Console displayed about 590,000 clicks over a selected 12-month period.
Did Chase use AI to write PeptIQ’s articles?
Yes. Chase described using AI for a substantial share of the content, alongside writing articles himself and hiring writers.
How did PeptIQ connect blog traffic to its app?
An educational article included a reconstitution calculator. Chase described a save action that guided people through account creation so their information could be saved into PeptIQ.
What tools do you need to build a subscription tracking app like PeptIQ?
Chase built PeptIQ with Vibecode, Expo, React Native, Supabase and RevenueCat, then hosted the marketing site on Vercel and grew it through search. A builder starting today could use Framer for the app landing page or Lovable as an AI app builder for a web prototype, but the part that did the work was content that answered real questions and led into the app.