ABOUT

We took the boring position on purpose

Adoption over configuration. Documentation over dependency. Saying no to work we’d do badly.

The origin (2 paragraphs)

Cirrusline started with a recurring frustration: watching competent implementations become shelfware because nobody had asked what the CRM was costing the people who had to use it. The pattern repeated across sectors and org sizes, and it was never a technology failure. It was a design failure with a technology bill attached.

So we built a consultancy around a narrower promise than most. We do one platform. We measure by usage. We write everything down and hand it over. And we’d rather lose a proposal than win it by agreeing to a scope we think is wrong.

What we believe (5 statements — no icons, type-led section, one of the few places the display face runs long)

1. An org is worth what people are willing to use. Fields shipped is not a measure of anything.
2. Documentation is a deliverable, not a courtesy. If losing us would hurt you, we designed it wrong.
3. Declarative first. Code is a maintenance commitment; it should have to justify itself.
4. The second year matters more than the first. Most value, and most decline, happens after go-live.
5. Say the inconvenient thing early. A hard conversation in week two is cheaper than a rescue in month nine.

How we’re structured

Small teams, long relationships. Every account has a lead consultant who stays with it — through build, through support, through the next phase. We deliberately don’t run a delivery pool model, because the knowledge of why a field exists is most of the value we accumulate.

We’re platform-focused rather than full-service. We don’t do web design, brand, or generic IT. When you need those, we’ll introduce you to someone who does them properly.

Certifications & partnership

Placeholder block: Salesforce Partner tier, number of certified consultants, certifications held by cloud. Populate with true figures or remove the section entirely — this is the first thing a technical buyer verifies.

Numbers

Same illustrative-metrics warning as the home page. Replace or delete.

Team

No photographs and no generated faces. Monogram tiles with name, role and a one-line specialism (“Integration architecture, ERP-heavy environments”). If you’d rather not name individuals at launch, use role tiles: Lead Consultant · Integration Architect · Data Engineer · Delivery Lead.