Why Business Software Shouldn't Start From Zero

When engineering leaders commission a custom software project, the ambition is almost always to create a competitive advantage: a faster quotation engine, a proprietary logistics routing algorithm, or a unified multi-subsidiary billing hub.

Yet in practice, engineering teams routinely spend the first four to six months building capabilities that have zero market differentiation:

• Multi-factor user authentication and password reset tokens
• Nested organization hierarchies and invitation flows
• Role and permission policy engines
• Database schema audit logging
• Asynchronous job queues and error recovery
• File upload validation, S3 storage keys, and thumbnail pipelines
• Outbound webhook dispatchers with backoff retries

This phenomenon—the Commodity Infrastructure Trap—wastes millions in capital expenditure and delays time-to-value.

The Hidden Cost of "Building from Scratch"#

Starting from an empty repository (git init) creates an illusion of pure freedom. However, each standard component incurs both initial implementation costs and perpetual maintenance overhead:

At typical European senior engineering contractor rates (€100–€150/hour), building this commodity layer costs between €60,000 and €125,000 before a single line of business logic is written.

Where Value Is Actually Created#

Business value is exclusively generated in the domain layer—the specific rules, formulas, workflows, and integrations that make a company distinct from its competitors:

The Platform Principle: Standardize the foundation. Customize the business.

+-------------------------------------------------------------+
|             Unique Business Domain (Value Driver)           |
|      Pricing Algorithms, Supply Chain Logic, Client APIs    |
+-------------------------------------------------------------+
|                                                             |
|   ===================== ALEGOR ==========================   |
|   Identity | Permissions | Audit | Workflows | Integrations |
|   =======================================================   |
|                                                             |
+-------------------------------------------------------------+
|               Base Infrastructure (Commodity)               |
|            Compute, Managed Databases, Object Storage       |
+-------------------------------------------------------------+

Architectural Cohesion vs. Patchwork Libraries#

A common response to the cost problem is assembling disparate third-party open-source packages. While better than writing everything from scratch, package sprawl introduces significant integration friction:

1. Incompatible Data Models: The auth package models permissions as flat strings, while the workflow package requires integer bitmasks.
2. Scattered Audit Logs: One package writes to a custom MongoDB collection, another to standard stdout, and the main app writes to PostgreSQL.
3. Upgrade Fragility: Major version bumps in underlying framework dependencies break uncoordinated third-party community packages.

A curated platform like Alegor unifies these capabilities around consistent architectural conventions (e.g., standard event dispatching, explicit contracts, and unified tenant scoping).

Summary Decision Matrix#

• Rebuild infrastructure from scratch only if your core product is infrastructure (e.g., building a competitor to Auth0 or AWS S3).
• For all application engineering initiatives, adopt a proven modular foundation to reach production 3x faster with enterprise-grade stability.

Read next: Architecture of a Modern Business-Critical Application or learn about our Security Architecture.