Update wiki/consulting-software.md
36e9709fedd6 harrisonqian 2026-04-12 1 file
index a0a4137..d328ea9 100644
@@ -20,4 +20,4 @@ a Palantir-style audit/plan/make software business — you go into a company, au
the interesting business model tension is between the consulting side (high-margin, relationship-driven, hard to scale) and the productization side (lower-margin per client but recurring revenue, scalable). the Palantir reference is deliberate — they built a specific workflow tool for every client, then productized the patterns that emerged across clients. the play here might be: start with a handful of clients in a specific vertical (e.g. small biotech firms, local schools) to build deep workflow knowledge, then productize the patterns into a SaaS product. the [[overnight-app-grinder|overnight app grinder]] and [[spec-driven-dev|spec-driven dev kit]] are directly relevant infrastructure — the faster and more reliably you can build software, the more profitable the per-client engagement.
-this connects to [[b2b-competitive-analysis|B2B competitive analysis]] as a possible first product in this model — competitive intelligence tooling is a clear pain point for B2B companies, is underserved by existing SaaS, and is scoped enough to deliver in weeks. the consulting path also connects to [[stress-testing-suite|stress testing suite]] and [[idea-tester|idea tester]] for the market validation discipline. sits in the [[cluster-hiring-work|hiring and work tools]] cluster because the primary buyer is an internal team or operations owner at a B2B company, not a consumer.
\ No newline at end of file
+related: [[b2b-competitive-analysis|B2B competitive analysis]], [[stress-testing-suite|stress testing suite]], [[idea-tester|idea tester]], [[cluster-hiring-work|hiring and work tools]]
\ No newline at end of file