One Platform, Many Small Apps — And Why We Stopped Building a Suite

Every business tool follows the same arc. It launches doing one thing unusually well. It grows. Two years later it does eleven things adequately, the settings page has fourteen tabs, and onboarding a new team member takes an afternoon.

We started down that road and stopped. Linkdra is now a platform of small apps rather than a suite — and the distinction matters more than it sounds.

Suite versus platform

A suite is one product with many modes. You buy all of it, you learn all of it, and the parts are entangled enough that you cannot really opt out of the bits you don't need.

A platform of small apps is the opposite arrangement: several narrow tools that happen to share infrastructure. What they share is deliberately boring:

• One login and one workspace
• One tenant model, so your team and permissions are defined once
• One billing relationship
• One white-label configuration, so your brand is set once and applies everywhere

What they do not share is scope. Each app does one job. You adopt them one at a time, you pay for them one at a time, and dropping one does not disturb the others.

Why this is better for professional services

Our users are accountants, real estate agents, contractors, consultants and small agencies. The common thread is that nobody has an IT department and nobody has a spare Thursday to learn software.

That reality has consequences:

1. Adoption has to be survivable solo. An app you can understand in twenty minutes gets used. A suite that needs a rollout plan gets bought and abandoned.
2. Needs do not arrive together. A firm needs prospecting help this quarter and vendor communication next year. Bundling forces them to buy the future today.
3. The brand is the business. For a small firm, anything a client sees has to look like the firm sent it — which is why white-labeling is platform-level here, not a per-app upsell.

How pricing follows the architecture

If apps are adopted separately, they have to be priced separately — otherwise you have a suite with extra steps.

So pricing works in two layers. The platform layer covers the workspace, the tenancy and the white-label configuration. Each app carries its own price on its own page, because the plan detail for a prospecting tool has nothing useful in common with the plan detail for a vendor communication tool.

The result is that "should we add this app?" is a small, reversible decision. That is the whole design goal.

What is live, and what is coming

One app is live today:

• Prospecting CRM — connection tracking, follow-up scheduling and qualification for people who sell by relationship rather than by funnel.

More are in progress. They will ship the same way: narrow, separately priced, and useful on their own the day they launch. If one of them is not worth its own line on your invoice, it should not exist.

Have a look at the platform or tell us what you need.