Loading page…
A front-office operating system and marketplace that helps manufacturers sell faster and gives buyers a quicker route to new products.
about 400 paid customers · roughly 80 new paid customers per month
In a trust-deficit, offline market, field sales is not a compromise; it is the product-distribution advantage.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Divyaanshu Makkar returned to entrepreneurship after consulting, running Connect2Teach, and spending a year at Bessemer Venture Partners. He and cofounders Vikas and Manuel chose manufacturing because it was a large, changing, under-digitized market with fewer fashionable competitors. Before writing production code, they spent four to five months meeting roughly 100 factories across Panipat, Moradabad, Jaipur, and other Indian manufacturing hubs, sometimes shadowing owners for weeks. The first concept became a SaaS-enabled marketplace after a Figma prototype attracted paid commitments. Sourcewiz started on the sales and marketing side of the factory because legacy ERP systems carried too much baggage. Its tools digitize catalogs, quotations, costing, trade-show follow-up, buyer inquiries, and product discovery. The first customer paid 30,000 rupees in November after a pro forma invoice. The team then used field sales to reach about 400 paid customers, with roughly 80 more joining each month, while testing marketplace demand with buyers in Dubai and elsewhere. The founder reported $200K–$250K ARR at the time of the interview.
For Sourcewiz, the first customers should come from the factory clusters where trust already travels through owners, export associations, and local business communities.
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: Founder interview; the $200K–$250K ARR, customer count, pricing, and marketplace traction are self-reported and unaudited. The transcript does not provide third-party financial verification.
Sourcewiz got its first payment when the team raised a pro forma invoice after taking an early customer through the product. The customer transferred roughly 30,000 rupees in November, two to three months after the first team member joined and while the product was still being tested with early users.
Sourcewiz created its flywheel by combining operational usefulness with dense local networks. A factory that receives faster inquiry replies, quicker customized catalogs, and cleaner trade-show follow-up gets value before the marketplace is fully mature.
Sourcewiz reduced the risk of a quiet market by replacing assumptions with structured observation. The founders kept a detailed Notion record of factory conversations, visited multiple manufacturing regions, and spent extended periods watching owners work.
Sourcewiz is a SaaS layer for manufacturers whose sales process historically ran through spreadsheets, paper catalogs, notebooks, trade fairs, and repeated phone calls. Its front-office tools digitize product information, answer buyer inquiries faster, calculate costs, create quotations, and generate customized catalogs. A buyer can upload a PDF mood board and receive a more relevant product set instead of a giant undifferentiated catalog. At trade shows, QR codes can connect physical products to digital catalogs and preserve the buyer relationship after the event. The broader ambition is an operating system for factories that eventually spans sales, marketing, production, and procurement. The marketplace extends the product beyond factory workflow: a buyer with a theme can discover products across categories and ask Sourcewiz to help bring new lines to market. The product is therefore two connected businesses, but the factory SaaS is the wedge. That wedge solves a clear pre-sales problem without asking a manufacturer to replace a deeply embedded ERP system.
Sourcewiz began with annual SaaS pricing, using the software as the entry point for a larger marketplace relationship. The first payment was about 30,000 rupees, while later annual deals reached 70,000, 100,000, and 180,000 rupees. The interview also describes conversations with larger factories willing to pay $5,000 or $10,000, and an average price point of about $500 at the earlier customer scale. The pricing strategy moved upward as the team learned that larger factories had more users, more products, and a more expensive operational problem. The marketplace can add take-rate revenue when buyers procure products through the network, but it was still early and the first orders were being closed. This is a sensible monetization ladder: charge for the factory workflow first, then charge for transactions and services once buyer demand is reliable. Annual contracts also reduce collection friction and give the team implementation budget. The risk is mixing low-priced SaaS, enterprise deployments, and marketplace economics before one motion is repeatable.
The transcript emphasizes process and field operations more than a named software stack. The early validation stack was deliberately light: a Figma prototype, recorded customer conversations, a Notion research base, and manual implementation. That kept product investment low until factories demonstrated willingness to pay. The heavier cost is people. Sourcewiz had to recruit and train field sales staff in tier-two cities, build local operating systems, and sometimes use interns to move product data from legacy formats into the platform. Customer onboarding is a material cost because the team aims to get a new customer live in less than 10 days. A software founder copying this model should measure sales travel, local hiring, implementation labor, support time, annual contract value, and customer retention separately. Automation should follow repeated manual steps rather than precede them. The eventual margin opportunity is strong if catalogs, costing, onboarding, and sales reporting become standardized, but marketplace operations and quality control can pull margins back down. The founder also described using weekly funnel reviews and decentralized ownership to prevent the business from depending on one executive.
Copy the disciplined discovery process, not the assumption that every B2B SaaS needs remote self-serve acquisition. Sourcewiz spent months inside factories, chose a front-office problem with less legacy baggage, charged for prototypes, and accepted field sales as part of the model. It also treated onboarding as part of the product, using manual data work when necessary to shorten time to value. Those choices are portable to other offline industries such as distributors, labs, and specialty wholesalers. Change the expansion sequence if the marketplace side is not ready. A new founder should first prove one repeatable workflow, one customer profile, one annual price, and one local acquisition loop. Only then add a buyer network or adjacent modules. Build stronger instrumentation around gross margin per customer and implementation hours than Sourcewiz could show in its early phase. Keep the product promise narrow enough for a field representative to explain in one visit. The best version of this idea is not a giant ERP replacement; it is a trusted operational wedge that earns the right to become infrastructure.
The main risk is that field sales grows faster than product quality. Sourcewiz explicitly worried about mis-selling, inconsistent representation, and losing control as the team expanded across tier-two cities. Training, certification, call reviews, and a clear handoff between sales and customer success are essential. Implementation drag is another threat: if a factory must clean thousands of products before seeing value, the contract can become an expensive services project. Marketplace expansion adds supply-quality risk, especially for handmade Indian products where consistency can vary. The buyer side also needs a repeatable acquisition model in the United States and Gulf markets; early relationships do not yet prove scalable demand. Finally, incumbent ERP vendors, local agencies, and marketplace platforms can copy individual features. Sourcewiz needs a defensible combination of trusted regional relationships, structured product data, fast onboarding, and transaction history. The business should conserve cash while testing new geographies, because every new country adds language, logistics, quality, and sales complexity. A narrow profitable hub is safer than premature global coverage.
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,435 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