Which business-size path should I choose?

Choose the path whose operating problems sound most familiar. Headcount is a routing guide, not a qualification test; a complex 200-person organization may need the mid-market path, while a focused division inside an enterprise may begin with a bounded assessment.

Does Applied Architecture Group work with both startups and enterprises?

Yes, but not with the same scope. Startups receive a focused systems-foundation path. Growing businesses typically begin with a Business Systems Assessment. Mid-market and enterprise work is bounded around a domain, decision, integration challenge, or modernization roadmap.

A scope matched to the organization

Choose the business-size path closest to your operating reality.

The problems change as a company grows. Startups need a clean foundation. Growing businesses need repeatable work and connected systems. Mid-market and enterprise teams need cross-functional architecture, governance, and disciplined modernization decisions.

Choose Your Path Not Sure? Talk It Through

Headcount is a guideVendor-neutralSenior-led and scope-first

Four different starting points

Pick the problems you recognize, not just the number.

The ranges overlap at the edges on purpose. A ten-person firm with simple operations may still be on the startup path; a rapidly scaling company may already need the growing-business path.

1–10 employees

Startup foundations

Make the first systems decisions well: ownership, customer tracking, documents, invoicing, security basics, reporting, and sensible automation.

Build the foundation → 10–250 employees

Growing business

Replace manual handoffs and disconnected tools with clearer workflows, reliable data, useful reporting, and a prioritized systems roadmap.

Create room to grow → 250–500 employees

Mid-market complexity

Align systems, data, integrations, ownership, and investments across functions without turning the work into an endless transformation.

Focus the architecture → 500+ employees

Enterprise architecture

Apply senior architecture judgment to a bounded modernization decision, platform boundary, data domain, operating capability, or AI-readiness question.

Explore enterprise support →

Different scale. Same discipline.

Every path begins with the work, the decisions, the data, and the people who own the outcome. Technology follows the operating need.

No software resale or platform commissions.
No inflated transformation scope when a focused decision will do.
No small-business shortcut applied to enterprise complexity.
A written scope, deliverables, and boundaries before work begins.

Common questions

Choosing a path.

What if we are right on a headcount boundary?

Choose the problem set that matches. Headcount is only a proxy for complexity. The first call confirms fit and adjusts the starting point before any scope is proposed.

Will a startup receive the same assessment sold to a 100-person company?

No. A 1–10 employee business usually needs a narrower foundation plan and guided decisions, not a full multi-workflow Business Systems Assessment.

Can enterprise work start small?

Yes. A bounded decision, domain, integration boundary, or roadmap can be the right unit of work. Large-company experience is useful precisely because it helps define the boundary and dependencies clearly.

Still between paths?

Describe the operating problem and approximate size. You will reach Andrew directly, and the first recommendation may be a smaller step than you expect.

Request a Free 20-Minute Call Browse All Services