KB Report: Business Idea Evaluation & Monetisation

Query: Evaluate my business idea and monetisation
Date: 2026-04-24
Sources used: wiki/ios-app-ai-second-brain.md, wiki/software-engineering-career-2026.md, wiki/business-model.md, wiki/obsidian-skills-for-claude.md, wiki/claude-code-obsidian-second-brain.md

What the Idea Actually Is

You have two business angles sitting in your vault, and they are related but distinct. It is worth being clear about which one you are pursuing.

Angle A — The iOS App (product business) A native SwiftUI app that brings the Obsidian + Claude Code second-brain workflow to iPhone. Local Markdown vault, screenshot → OCR → structured note, AI diary and memory layer via user-supplied API keys, on-device RAG. Monetised via 14-day free trial + Pro subscription ($4.99–$9.99/month or $49–$89/year).

Angle B — AI Automation Consulting (services business) Land contracts helping businesses automate processes and reduce headcount overhead using AI. You guide the AI using your engineering experience; the AI writes the code. Already validated by the ex-Meta engineer in your vault who built a 20,000-line client app without writing a single line himself.

These are not the same business. Angle A is a product with recurring revenue but requires sustained marketing and retention work. Angle B generates immediate cash but doesn't compound the same way. Your wiki currently treats them as a single "business model" entry — that is the first thing worth clarifying.

Evaluation: The iOS App (Angle A)

Strengths

Genuine differentiation exists. Your competitive matrix tells the story clearly:

| App | Markdown-first | Local files | User API key | Screenshot→MD | |---|---|---|---|---| | Reflect | ✅ | ✅ | ❌ | ❌ | | Mem.ai | ❌ | ❌ | ❌ | ❌ | | Your app | ✅ | ✅ | ✅ | ✅ |

No existing app in the space combines all four. User-supplied API keys in particular is a strong privacy and cost story — you never touch their data, you never pay their inference bills. That is a compelling combination for the Obsidian-adjacent audience who already understand and care about data ownership.

The target user is self-selecting and high-intent. People who know what Obsidian is, who use Claude Code, who clip articles to raw/ folders — these are not casual users. They are exactly the kind of people who pay for tools that make their workflows better. They also tend to write publicly about what they use, which is free distribution.

The timing is right. The Claude Code + Obsidian wave is cresting now. Your own vault has 10+ sources on this topic clipped in a single month, all from April 2026. This is not a mature market — it is early enough that being first with a polished native app matters.

The tech stack is aligned with your skills. SwiftUI + Hummingbird is something you can build. You are not proposing to learn a new language or framework — you are applying existing Swift knowledge to a problem you personally experience and understand.

Risks and Weak Points

The Obsidian audience is small and technical. This is also the risk. The people who want this app are few, they are opinionated, and many of them will just build their own version. You need to decide whether you are building for that niche (lower volume, high conversion, strong word-of-mouth) or whether you are building something more accessible that uses the second-brain idea but does not require the user to know what a Markdown vault is.

User-supplied API keys are a friction point at onboarding. Asking a new user to go get an Anthropic API key before they can use the core feature will kill conversion for anyone who is not already technical. You need either a hosted AI tier (you absorb the cost, price it in) or a very smooth onboarding that makes the API key setup feel like two taps rather than a developer task.

The 14-day trial window is correct but only if the "aha moment" arrives early. Your wiki notes this directly: the trial needs to be long enough for the user to feel "it's learning me." That requires the user to actually add content in the first few days. If they install, open once, and close — the trial is wasted. The onboarding flow needs to pull content in on day one, not wait for the user to discover the habit on their own.

Competition from Obsidian itself. Obsidian's mobile app exists and is improving. If they add native AI features — which is a reasonable thing to expect — your differentiation narrows. The user-supplied API key angle and the tighter AI memory layer are your moat. Lean into those hard.

Evaluation: The Monetisation Model

Pricing

$4.99–$9.99/month is correct for the market. Reflect charges ~$10/month and Mem.ai charges ~$12–15/month. You are not underpricing relative to comparable tools, which is good — underpricing a productivity app signals low confidence and attracts churners.

The annual plan ($49–$89/year) is important. Annual subscribers churn at a fraction of the rate of monthly subscribers and dramatically improve your LTV. Make the annual plan the default selection on the pricing screen, not something users have to hunt for.

Free Tier

Your wiki defines the free tier as: basic Markdown notes, screenshots → text, local storage, limited AI. This is the right shape. The free tier should be genuinely useful — enough that users build a habit — but limited in the one dimension that matters most: AI queries. Capping the number of AI interactions per week (rather than capping features) is a cleaner conversion lever because the user hits the wall exactly at the moment when they are getting value, which is the best moment to convert.

The User-API-Key Model vs. Hosted AI

You have a choice here that has significant revenue implications:

Option 1 — User supplies their own API key (current plan)

You pay zero inference costs
Privacy story is excellent
Conversion is harder for non-technical users
Revenue ceiling is lower (technical users are a smaller market)

Option 2 — You host the AI, price it in

Broader market (no API key required)
Inference costs are real but manageable at small scale (~$0.003 per 1K tokens on Sonnet)
Stronger conversion because onboarding is frictionless
You own the relationship with the model provider and can switch

Option 3 — Both (tiered)

Free / Pro with user API key: privacy-first tier
Pro+ with hosted AI: you handle everything, higher price point (~$14.99/month)

Option 3 is worth considering. It lets you serve the technical Obsidian audience with Option 1 while opening the door to a broader audience with Option 2 — without cannibalising either.

Evaluation: The Consulting Angle (Angle B)

This is lower risk and faster to first revenue. The ex-Meta engineer in your vault is already doing it: landing contracts to automate business processes, using AI to write the code, using his experience to guide the output. A 20,000-line client app without writing a line is a strong proof of concept.

For you specifically, the consulting angle has one significant advantage: it funds the iOS app. Consulting revenue is immediate. App revenue is delayed by months of building, App Store review, and user acquisition. If you pursue both in parallel — consulting to generate cash, iOS app as the compounding asset — you reduce the financial pressure on the product to succeed immediately.

The risk of consulting is that it expands to fill all available time and the product never ships. Set a hard boundary: consulting is capped at X days per week, the rest goes to the app.

What Your Wiki Does Not Yet Cover (Gaps)

Three things are missing from your knowledge base that are directly relevant to this decision:

App Store economics — conversion rates from free trial to paid, average revenue per user for productivity apps, App Store's 30% cut (15% for subscriptions after year one via the Small Business Programme). You do not have a source on this.
User acquisition strategy — your wiki has the ex-Meta engineer's advice to document publicly on social media, but no concrete plan for how you specifically would reach the Obsidian + Claude audience. That audience is on X, YouTube, and Reddit (r/ObsidianMD, r/ClaudeAI). These are not general audiences.
Regulatory / privacy specifics — the privacy story (local files, user API keys) is a selling point, but you have not captured anything about GDPR, App Store privacy nutrition labels, or what "encrypted sync" via Hummingbird actually requires in practice.

Summary Verdict

The iOS app idea is sound and differentiated. The timing is good, the tech stack is right, and the competitive gap is real. The monetisation model is correctly priced for the market. The main execution risks are: onboarding friction from the user-API-key model, the small size of the initial target audience, and the risk that consulting work crowds out building time.

Recommended next steps, strictly from your wiki:

Decide: Angle A, Angle B, or both in parallel with a time split
If both: consult to fund, cap consulting days, protect building time
Resolve the hosted-AI vs. user-API-key question before writing any onboarding code — it changes the entire first-run experience
Consider the tiered pricing model (user API key tier + hosted AI tier at higher price)
Document your building process publicly from day one — this is both marketing and accountability

Sources: wiki/ios-app-ai-second-brain.md · wiki/software-engineering-career-2026.md · wiki/business-model.md · wiki/obsidian-skills-for-claude.md · wiki/claude-code-obsidian-second-brain.md

kb-report-20260424-business-idea-evaluation