Loading page…
A Toronto software studio grew custom web and enterprise development into a founder-reported $8M ARR business.
founder-reported
A warm introduction to one restaurant-equipment seller became nearly $100K of repeat work, but the founders say they regret waiting so long to build their own software product.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Vishal Patel and his cofounder started CodePaper in Toronto while Vishal was studying computer science at York University. They first considered an import business, then chose IT services they could deliver themselves: websites, software development, and custom systems for companies. A relative introduced them to James, a restaurant-equipment seller who needed an online ordering site. A project initially worth about $3,000–$4,000 grew into nearly $100,000 of work over three or four years. The founders handled delivery themselves, then built a six-person in-house team in Surat and used project management software to assign tasks. They describe the current company as a Toronto-based technology business at $8M ARR. The service operation also generated savings that they later invested in restaurants, though Patel says he regrets the operational burden and wishes they had built proprietary software earlier. Their newer product, Uplift AI, applies that product ambition to helping businesses appear in AI-generated answers.
CodePaper’s first customer came through a relative who introduced Vishal Patel to James, a restaurant-equipment seller opening an online shop. The founders had told friends, classmates, and relatives that they were doing website and software work; that repeated word of mouth created the introduction.
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.
Data credibility: Vishal Patel says CodePaper is an "$8 million tech company" at $8M ARR; later in the same interview the host also frames "$8 million" as the overall business built since 2017, which includes restaurant investments, so the split between software revenue and other holdings is unclear. The first-client price (about 3,000–4,000), the nearly $100K of repeat work from that client, and first-year revenue are founder-reported. No audited statements, invoices, or customer records are shown, and the currency basis is not always stated.
The first dollar arrived as cash for a custom e-commerce and online ordering website for the restaurant-equipment seller; the amount is recalled as roughly $3,000–$4,000. The founders had no completed portfolio at that stage, so they sold a specific result: let buyers browse a large catalog and place orders online.
CodePaper’s early flywheel joined repeat work to a delivery system. The first customer kept assigning projects for several years, while the founders continued telling people around them what the company could build.
The founders were students with little money, and early prospects did not automatically believe that two young people could deliver business software. They kept talking about the company while juggling classes and restaurant night shifts, then built client projects overnight.
CodePaper is a custom software and IT-services business, not one fixed application. The founders describe building websites, online ordering, custom software, and products for enterprise clients. Their early restaurant-equipment project needed a catalog and ordering experience; later work was divided between the founders in Toronto and a delivery team in Surat. A task-management system helped turn incoming projects into plans and assigned work, with a project manager coordinating the employees. Our read: sell the service around a specific business bottleneck, then use the same project patterns repeatedly. Reusable modules for catalog import, account permissions, payment status, and order operations can reduce delivery time without forcing every customer into the same product. Keep the client-facing promise tied to the business result and the custom code needed to achieve it.
The revenue model is project-based software development and enterprise delivery. The first described website was priced around $3,000–$4,000, and one customer later bought roughly $100,000 of work over three or four years. Patel describes CodePaper as an $8M ARR company today, but the interview does not break that figure down by service line, client count, or recurring contract mix. Our read: a studio at this scale needs to distinguish one-time builds from retainers and recurring platform work. Quote discovery, implementation, change requests, hosting, and ongoing support separately so customers understand what they are buying and the team can see which work creates margin. A repeat customer is valuable, but no single account should become the only reliable source of cash. Use the early project to establish a commercial relationship, then earn expansion through additional defined outcomes rather than unlimited custom work.
The founders mention computer-science training, a task-management tool, a project manager, and a delivery team in Surat. They initially did the work themselves and brought in an India-based contact for smaller implementation tasks before creating a six-person in-house team. The company started from a student basement and later operated from Toronto with delivery work assigned across locations. They describe the service as profitable, but operating costs and current margins are not supported by a clear breakdown. Our read: retain a lean core team and staff delivery against signed work, not optimistic pipeline. Track utilization, rework, payment collection, and support hours by project. Use a standard technology baseline, written access controls, code review, backups, and client handover documentation so distributed work does not create security or maintenance gaps. Price project management and quality assurance as part of delivery rather than treating them as invisible overhead.
Copy CodePaper’s willingness to sell a service the founders could actually deliver, its persistent local word of mouth, and its move toward a structured delivery team once demand justified it. The first customer came through a trusted introduction, then expanded into substantial repeat work; that is a practical path for a founder without a large advertising budget. Change the early portfolio tactic: the founders said they showed examples of work they had not yet completed for clients. A new studio should use clearly labeled demos, open-source examples, or a small paid pilot instead. The founders also describe regretting that they spent years delivering other companies’ products without making their own. Our read: reserve capacity for internal tooling or a focused product experiment, but only after delivery economics are stable. Choose a narrow repeated problem from client work and test whether multiple buyers will pay for the same solution before turning it into a standalone SaaS.
A services firm can grow revenue while remaining dependent on the founders’ ability to sell, scope, and rescue projects. Custom work also creates delivery risk when requirements are unclear, clients change direction, or offshore handoffs lack review. A large repeat customer may help the studio build momentum, but it can also hide weak diversification if new accounts are not added. Patel’s own regret is that CodePaper did not launch a proprietary product sooner, while the restaurant investment became a separate, operations-heavy distraction. Our read: protect the core business with signed scopes, milestone billing, documented ownership of code, and a clear support boundary. Keep an account concentration view and a delivery forecast alongside top-line revenue. Product bets should come from repeated customer pain and paid validation, not from the emotional appeal of owning software. The reported $8M ARR is founder-reported and does not establish that another small studio can reproduce the same path or margins.
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