IL Signal Studio

Case Study · AI Product Build · 2026

A repeatable call-preparation system
for sales conversations

PitchOS is a native iOS app that uses Claude to generate a structured pre-call brief from the deal details a user provides. The brief covers a prospect snapshot, likely priorities, key risks, a recommended focus and a suggested opening question. Built with Swift and an authenticated Supabase Edge Function. Live on the App Store.

PitchOS Pro website screenshot
iOS structured sales-call preparation
Swift native, not a web wrapper
Live on the App Store

Pre-sales reps had no repeatable system.

Discovery calls tended to start the same way: manual research, re-reading CRM notes, scanning LinkedIn, and trying to anticipate objections with no structure. The preparation was inconsistent, and the gaps showed in calls.

For founders running their own sales, the problem was worse. No dedicated pre-sales resource, no playbook, and no time to build one. Sales calls often began without a repeatable preparation process.

A deal brief in one tap.

The user enters the company, contact, role, deal stage and their own notes. Those details go to an authenticated Supabase Edge Function, which calls Claude and returns the brief. There is no web search or live-source lookup: the brief is built from what the user supplies.

The app is built natively in Swift, not a web wrapper. The same Edge Function also backs question, objection, summary and email generation. StoreKit 2 manages subscription state and receipt validation on-device.

Briefs are saved to the user's account, so a brief generated earlier can be reopened before the call rather than regenerated.

Preparation follows the same structure.

The meeting-brief prompt requests five named sections: Prospect Snapshot, Likely Priorities, Key Risks, Recommended Focus and Suggested First Question. Generated briefs are saved to the user’s account after generation, so preparation is explicit rather than improvised.

The subscription model went live with StoreKit 2 on launch day. No payment infrastructure to manage separately; everything is handled natively inside the App Store ecosystem.

What it was built with.

Swift Native iOS, UIKit + SwiftUI components
Claude Brief generation via Supabase Edge Function
StoreKit 2 Subscription management, receipt validation
iOS 17+ Minimum deployment target

Why this matters

PitchOS proves IL Signal Studio can ship a complete product, not just an automation or a workflow. Design, native development, AI integration, and App Store monetization, end to end. If you have a workflow problem that needs a real product, not a SaaS subscription, this is the kind of build we do.

Have a workflow that needs the same treatment?