The Foundry Thesis on Small-Business Software

There's a strange thing that happens to business software. It starts simple.

Then somebody asks for one more feature. Then a larger customer asks for another. Then a team needs permissions. Then somebody wants custom workflows. Then dashboards. Then automation. Then reporting. Then another dashboard to explain the first dashboard.

Eventually the software can run a huge company. And the person with a small business opens it and thinks: Where do I put the job?

More Isn't Free

Software companies talk about features like they're free. They aren't. A feature costs code. It costs maintenance. It costs documentation. It costs support.

But the customer pays another cost too. Attention. Every button on a screen creates a question. Do I need this? Should I fill this out? What happens if I don't? Am I using this wrong?

The more a product can do, the more it has to explain what it can do. That's fine when complexity is the thing you're buying. It's terrible when you just wanted somewhere to put your customers.

The Small-Business Loop

Most small businesses are variations of the same loop.

• Someone needs something
• You figure out what they need
• You agree on the work
• You do it
• You get paid
• They might come back

That loop can become incredibly complicated. There can be employees, subcontractors, materials, regulations, financing, scheduling and a thousand edge cases. But the center stays recognizable. Customer. Work. Money.

That should be the center of the software too.

The Customer, Not the Pipeline

A strange thing happens when sales software becomes business software. Every human starts looking like a sales opportunity. Lead. Prospect. Deal. Pipeline. Stage. Probability.

That makes sense if your primary job is selling. But the guy whose air conditioner you repaired last Tuesday is not a “won opportunity.” He's John. He lives on 42nd Street. He had a broken condenser. He paid you.

That human model matters. Foundry starts with the customer, not the pipeline.

A lot of software is flexible because you can configure it. That sounds great. But configuration has a hidden implication: the product does not yet know how you work. So you have to teach it.

Foundry takes the opposite position for the basic things. A customer is a customer. A job is work. An estimate tells somebody what the work should cost. An invoice asks them to pay. A receipt says they did. These concepts are already familiar. The interface should use that familiarity.

Simple Does Not Mean Small

There's a tendency to talk about simple software like it's software you eventually graduate from. We don't agree.

Simple should mean the complexity is controlled. Not absent. There can be serious infrastructure underneath a simple interface — authentication, permissions, localization, billing, data integrity, communication systems, infrastructure.

None of that requires putting infrastructure language in front of the customer. The product can get stronger without getting louder.

Localization Isn't Translation

This matters even more once software crosses borders. The lazy version of globalization is: build an American product, translate the strings, change the currency symbol, done.

That isn't how businesses work. The words people use are different. The expectations are different. Payment habits are different. Pricing tolerance is different. Even what sounds trustworthy is different.

Foundry is built as a family of market-native surfaces. The U.S. product can be Foundry. Other markets can carry the names, language, pricing and presentation that make sense there. The underlying system can stay coherent without pretending everybody runs a business the same way.

There are products that should have dispatching, fleet tracking, advanced sales automation, deep project management, enterprise reporting. Those products should exist. Foundry does not need to become all of them. The goal is not to win a feature checklist. The goal is that somebody opens Foundry and immediately understands their business.

The Standard

We keep coming back to the same test. Can you see the customer? Can you see the work? Can you see the money? Can you tell what happens next?

If yes, the system is doing its job. If the answer requires another dashboard, we should probably keep working.

Clients. Jobs. Money. Under control.

Start using Foundry →