TetraCore operates six SaaS products: FourSight (uptime monitoring), CallsAround (AI receptionist and emergency dispatch), LinkPilot (link management), ItemStage (chain-of-custody item workflows), Franexis (franchise operations), and VoterCXM (civic engagement). Six products, one small studio in Bowling Green, Ohio.
Conventional wisdom says this is a mistake — pick one thing, focus. The conventional wisdom is not entirely wrong, and this post is honest about where it bites. But running a portfolio has taught us things a single product never would have, and those lessons are the point of writing this down.
Shared infrastructure is the only way this works
Six products cannot mean six of everything. The portfolio survives because the boring layers are shared: common deployment patterns, common authentication approaches, a common design system, common conventions for status pages, privacy pages, security pages, and pricing pages. When we improve how one product handles something, the improvement is a template the other five inherit.
The discipline this forces is underrated. A solo product can accumulate one-off decisions forever. A portfolio punishes every snowflake immediately, because every one-off is something a very small team now has to remember six times. We say no to clever custom architecture not out of virtue but out of arithmetic.
Every product ships llms.txt, schema, and a status page
A pattern we adopted portfolio-wide: every product publishes machine-readable descriptions of itself — structured data (schema.org markup), an llms.txt file for AI assistants, and a public status page. Partly that is modern SEO reality: people increasingly ask ChatGPT or Google "what is ItemStage?" or "who makes FourSight?", and the answer gets assembled from whatever machines can read. If you do not describe your own products precisely, something else will describe them imprecisely for you.
But it is also just operational honesty. A status page is a promise made in public. Structured data forces you to state plainly what the product is, what it costs, and who is behind it. Doing that six times over, consistently, is how a small parent company becomes a coherent entity rather than six disconnected websites.
Dogfooding is a strategy, not a slogan
FourSight, our uptime monitoring product, monitors the rest of the family. When a product in the portfolio has a bad night, our own pager knows before any customer does — and every gap we find in FourSight while depending on it becomes a fix that ships to every FourSight customer. There is no sharper product feedback loop than needing your own product to work.
The same principle built ItemStage. It was developed in cooperation with Millers Restoration, a real restoration company, inside a working restoration facility — where items arrive by the truckload and chain-of-custody is not a feature request but a daily operational fact. Products built inside real operations come out shaped differently: fewer speculative features, more of the unglamorous ones that only matter when you are actually doing the work.
Flat, transparent pricing is a portfolio discipline
With six products, we cannot afford six bespoke sales processes, so every product publishes flat, transparent pricing. What started as a constraint became a conviction. "Contact us for pricing" is a tax on the buyer's time and a tell about the seller's incentives. Published pricing forces us to know what our products are worth, keeps the sales conversation about fit instead of negotiation, and — at portfolio scale — is the only model that does not consume the team entirely.
What breaks when you run many small products
Honesty section. Three things quietly break at portfolio scale, and all three broke for us before we fixed them.
Support routing. A customer with a problem does not care about your org chart. Six products means six front doors, and requests arrive at the wrong one constantly. We had to build deliberate routing — clear support entry points per product, plus a central support page at the studio level — so no ticket depends on the customer guessing our internal structure.
Brand consistency. Six products drift apart by default — voice, visual design, even how each one describes its parent company. Left alone, the portfolio starts to look like six unrelated companies, which wastes the trust each product earns. The fix is unglamorous: shared design system, shared copy standards, and every product saying "a TetraCore product" the same way, everywhere.
Entity SEO. The subtlest one. Search engines and AI assistants have to learn that FourSight, CallsAround, LinkPilot, ItemStage, Franexis, and VoterCXM are one family with one parent — and they will not infer it. It has to be stated explicitly and identically on every site: structured data linking child to parent, consistent naming, reciprocal links. A single-product company gets this almost for free; a portfolio has to earn it deliberately.
What we'd tell anyone attempting this
Share everything boring. Dogfood ruthlessly. Publish your pricing. Describe yourself in formats machines can read, because machines are increasingly who gets asked about you. And accept that the portfolio itself is the product: the consistency across six small products is worth more than any individual feature in one of them.
The six products are all live — browse the portfolio and try them. And everything we learn operating them flows directly into the custom software work we do for clients; more on the studio itself is on our About page.