Steinhoff Group

Steinhoff Systems · the software side

Software built for an industry, or built for you specifically.

Two ways to buy software from the same team. The first is a product built once for a specific industry and sold as a subscription to every company that runs on it — the same logic as any vertical SaaS, aimed at the operational core of one industry rather than a horizontal feature every business needs a little of.

The second is the opposite direction: a system built once, for one company, because nothing on the market fits how that company actually runs. That's systems-integration and custom-development work — acting as the outside engineering team for a business that needs software built to its own process, not the other way around.

Where this actually is

New. No vertical SaaS product has shipped yet, and no custom engagement has closed. What's published here is the pricing model each line will run under once one does — not a track record. If you're the first conversation, you're the first conversation; that's said upfront rather than papered over with a case study that doesn't exist.

Two lines, priced differently

A product sold to many, and a system built for one. Different buyers, different risk, different pricing — kept as two businesses rather than blurred into one.

01

Vertical SaaS

One product, built for one industry, sold to every company running on it.

Built once and sold as a subscription to many companies in the same industry — an operating system for a specific vertical rather than a general tool with that industry's logo bolted on. The starting point is always the same question: what does this industry do every day that generic software handles badly, because it was never built for this industry's actual workflow?

Priced like enterprise software because it's sold to businesses that measure the cost of bad tooling in hours, not preference. Per-seat or per-workflow pricing, scaled to the value the product actually replaces — a manual process, a spreadsheet held together by one person's memory, or a horizontal tool being bent into a shape it wasn't designed for.

  • Built for one named vertical, not a horizontal tool with industry branding
  • Priced per seat or per company, tiered to the size of the operation running it
  • A real onboarding and migration path off whatever the industry uses today
  • The product is owned by Steinhoff Systems — not a work-for-hire build

Pricing model

Tiered subscription, priced per seat or per company depending on the vertical.

Team

✎ EDIT — from ~$400–800/mo

A single operating team inside one company. Core workflow only.

Company

✎ EDIT — from ~$2,000–5,000/mo

Full company deployment across multiple teams, with the integrations the vertical actually needs.

Enterprise

✎ EDIT — custom

Multi-site or multi-entity deployment, dedicated support, and contract terms matched to enterprise procurement.

Every figure here is a placeholder model, not a published price list — the real numbers get set against the first vertical actually chosen, and against what that industry's current tooling costs to replace.

02

Custom enterprise development

The outside engineering team for a system nothing off the shelf can be.

Acting as a software consultancy and systems integrator: building the specific system a company needs when the honest answer to "why not just buy something" is that nothing on the market actually fits how the business runs. Legacy-system replacement, internal tooling, and integration work that has to survive contact with a real operation on day one.

This is not the same business as Acro Studios. Acro builds marketing sites and product interfaces for clients; Systems builds and owns the harder, more structural software a company runs its operations on — the kind of engagement with a scope, a spec, and a support contract behind it, priced accordingly.

  • Discovery and a written technical spec before any commitment to build
  • Fixed-scope delivery, or a dedicated team on retainer for ongoing systems work
  • Integration with the client's existing stack, not a rip-and-replace by default
  • A support and maintenance contract, not a handoff into silence after launch

Pricing model

Project-based for defined scope, or a monthly retainer for ongoing systems work — priced at a premium day-rate reflecting senior, direct-founder-involved delivery rather than a bench of juniors.

Fixed-scope build

✎ EDIT — from ~$25,000

A defined system, spec'd up front, delivered against a fixed price and timeline.

Retained systems team

✎ EDIT — from ~$8,000–15,000/mo

Ongoing development and integration work, billed monthly, scoped quarter to quarter.

Enterprise systems integration

✎ EDIT — custom

Multi-system integration or a legacy-replacement programme, scoped and priced per engagement.

Premium positioning by design — this line competes on being the outside team a company trusts with the system its operation actually depends on, not on being the cheapest quote in the room.

Start a conversation

Tell me what the current system actually costs you — in hours, in errors, or in the one person who has to remember how it all works — and whether that's an industry-wide problem or one specific to how you run.

neo@steinhoff.group
Systems · Steinhoff Group