How I Built a Learning Platform in Weeks — by Building the Platform First

Most founders face a choice: build fast on someone else's platform, or build slow on your own. I accidentally found a third option — build your own platform first, then build everything else fast on top of it.

This is the story of how Horizech Workspace, a modular SaaS engine I've been building for two years, let me ship Wiscademy (a course platform for Canadian engineering licensing exams) in weeks instead of months.

The problem with starting from scratch every time

I've been a software engineer for over a decade. Every new project — whether it was a risk-management platform for Italian fintech clients, a mining safety system, or a password manager — needed the same boring infrastructure: authentication, authorization, a database layer, file storage, email, encryption, payments. Each time, I'd wire up the same pieces slightly differently.

At some point I stopped and asked: what if the infrastructure was already there, and I just had to build the application?

What Horizech Workspace actually is

Workspace is a modular engine built on .NET Core and React. Instead of a monolithic framework, it uses a Provider/Plugin/App architecture:

• ·Providers define capabilities as interfaces — Database, Auth, Media, Email, Payments, Encryption, and about a dozen more.
• ·Plugins implement those interfaces concretely — PostgreSQL for the database, Stripe for payments, S3 for storage, SMTP or SES for email. Swap one plugin for another without touching application code.
• ·Apps are the actual products — they just consume the providers and focus purely on business logic.

There's a package registry at hub.horizech.com where components are versioned and installed through a built-in manager, and a licensing system that handles both managed (cloud) and self-hosted deployments.

Think of it as the plumbing and electrical of a building. Once it's in place, building a new room is fast — you're not re-running pipes every time.

Wiscademy: the proof

When my co-founder (a licensed Canadian engineer) and I decided to build a platform for NPPE exam prep, the conversation went like this:

• ·Courses with structured content? Already had the Collections and Content providers.
• ·User authentication and accounts? Identity Authentication Plugin, already working.
• ·Payments? Stripe Payment Gateway Plugin, already integrated.
• ·Certificates for completed courses? A new feature — but built on existing providers, so it was days of work, not weeks.

The actual Wiscademy-specific code is a Next.js frontend that calls Workspace API actions. The entire backend — auth, data, payments, media, email — was already there. We went from "let's build this" to a working product with Stripe payments and a certification system in weeks.

The same engine, different products

Wiscademy wasn't the first proof. Before it:

• ·ProjSafe — a mining safety management platform with real-time job monitoring, hazard tracking, QR-based equipment management, and compliance dashboards. A completely different industry, built on the same engine.
• ·CaptainPassword — a self-hostable password manager. Built in days, because it just needed the existing encryption and auth providers.

Each product is different. The infrastructure underneath is the same.

What I learned

Building a platform before building products sounds backwards — and for most people, it probably is. I didn't plan it this way; Workspace grew out of years of frustration with rewiring the same infrastructure. But now that it exists, the compound effect is real: every new product starts at the application layer, not the plumbing layer.

The tradeoff is honest, though: Workspace took two years of nights and weekends alongside client work. It's not a shortcut — it's a long investment that's now starting to pay off in speed.

If you're an engineer who keeps rebuilding the same auth/database/payment stack for every project, the question isn't whether to build a platform. It's whether you can afford the patience to build it before you need it.

Syed Zeeshan Akhtar is a project manager and tech lead, and the founder of Horizech. More at zeeshan.website.