Loading page…
A simple link, QR, or kiosk attendance workflow that grew to about $30K MRR.
previously $2K–$3K MRR for an extended period
The wedge was not a complicated attendance suite: it was getting from a spreadsheet to a usable check-in in one drag and drop.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
OneTap Check-In is an attendance and check-in product built around links, QR codes, and kiosk use. Founder Karthik traces its origin to a University of Toronto dorm conversation: a dorm-mate who worked at MLSE, the Toronto company behind the Raptors and Maple Leafs, said its membership program still signed visitors in on paper, needed retention data, and disliked existing tools that charged per event. He and a friend built an iOS prototype and prepared it for a pilot/demo. The first customer was an enterprise client; the product later launched on the App Store. Karthik says the business spent a long period at $2K–$3K MRR and is now at about $30K MRR. He credits simple drag-and-drop Excel setup with helping activation and says App Store search for “check-in app” brought organic users during 2018–2019, when competition was lower. The team is still working on churn and retention; courses and classes with attendance requirements were a stronger recurring use case. All financial figures are founder-reported.
For attendance software, the first customers are often organizations already collecting names on paper. OneTap Check-In started with a dorm connection to someone at MLSE who described paper sign-ins for physical members and a need for retention and engagement data.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself. The exact words are quoted below, with a timestamp that jumps to the second each figure is said.
“But yeah, for the longest time we were stuck at like the 2K MRR, 3K MRR.”
10:29 · hear it in the videoData credibility: Founder Karthik reports the first enterprise customer, early App Store monetization, a $2K–$3K MRR plateau, and current revenue of about $30K MRR. The figures are self-reported and unaudited; no third-party data is cited.
Karthik says OneTap Check-In monetized early with its first enterprise client, then added in-app payments after its App Store launch. A first paid contract for attendance software can replace manual entry, intern time, or per-event tools.
OneTap Check-In’s simple activation helped users: the founder describes dragging and dropping an Excel file and seeing it appear in the product. App Store search for “check-in app” also brought organic users in a less crowded period around 2018–2019.
OneTap Check-In spent an extended period around $2K–$3K MRR before reaching about $30K MRR, according to its founder. During a plateau, segment retention before adding features.
OneTap Check-In should stay centered on its core customer job. Build a clear path from the customer’s first input to a finished result, with status and next steps visible throughout. Make the common case quick and predictable before adding settings for unusual cases. Keep onboarding inside the workflow: show a sample, explain required fields, and let a user complete the first meaningful task without a call. Collect feedback at the point where users hesitate, and distinguish a recurring need from a single customer’s preference. For a small vertical product, fit with the buyer’s daily routine is part of the product itself. Reliability, data portability, and clear support can matter more than a long feature list.
Price OneTap Check-In around the value and frequency of the workflow. Make the first paid commitment easy to understand, with clear limits, billing cadence, and a direct explanation of what happens after a trial. Track paid use separately from free trials, pilots, or verbal interest. For each customer, compare revenue with onboarding time, support, payment costs, and any ongoing manual service. If usage is seasonal or episodic, test pricing that matches the buying rhythm; if the task recurs weekly, subscription pricing may align better. Avoid deep discounts without an end date and a clear conversion condition. Review conversion and retention by customer segment so a headline revenue number does not obscure an unprofitable or one-time cohort.
Start with a dependable application that supports the primary workflow, billing, and basic reporting. Keep hosting, software services, payment fees, and founder support time visible per customer. Use managed infrastructure while volume is small, but establish backups, access controls, and data export early. Avoid storing more sensitive information than the workflow needs. A vertical SaaS can appear to have excellent software margins while implementation and support consume founder hours, so record those hours from the first pilot. Automate repeated setup steps only after several customers need the same thing. Review costs monthly and make infrastructure changes in response to real usage, security, or reliability needs rather than speculative scale.
Copy the discipline of starting with a specific customer and observable workflow. Speak with buyers before expanding the feature set, demonstrate the product using their real task, and ask for a paid pilot with a measurable outcome. Change the packaging and onboarding for the segment that shows repeated use and a reachable buyer. Keep a simple funnel: qualified conversation, demo, trial or pilot, first completed workflow, payment, and repeat usage. Review where prospects stop and use their words to improve the offer. Create reusable templates for onboarding and sales, but do not turn each account into a custom project. Evidence of repeatability comes from multiple customers succeeding through roughly the same process.
The main risk for OneTap Check-In is mistaking a functioning product or a single paying account for a repeatable business. Buyers may resist migrating from a familiar process even when the new tool works. Long sales cycles, one-off usage, customer-specific requests, and high-touch onboarding can consume more time than the revenue supports. Track why prospects decline and why customers stop using the product. Protect the product’s focus with a clear customer profile and a rule that custom work must serve a reusable need or justify its cost. Compare acquisition effort, onboarding time, support burden, and retention across segments. If adoption stays weak, revisit the buyer, switching offer, or workflow before adding more features.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click