Aligno
Lock the scope. Protect the margin.
Be among the first to get access
Scope creep is a setup failure
Ask any agency owner or freelancer about scope creep and you'll get the same answer: it's their number one profitability killer. Not bad clients. Not poor project management. The problem starts before the project does.
The typical project setup looks like this: a PDF proposal goes out, the client approves it via email, and work begins. The proposal says something like "up to 5 pages" and "2 rounds of revisions." But what counts as a page? What counts as a revision? When the client asks for "just a small change" to the navigation on week three—is that in scope?
Nobody wants this fight. The client genuinely believes they're asking for something reasonable. The agency genuinely believes they're being taken advantage of. Both are right, because the agreement was never specific enough to resolve the dispute unambiguously.
Industry research consistently finds that 79% of agencies deliver more work than they're contracted to—and the majority of that over-service is driven by unclear scope boundaries, not bad project management. The problem is systemic, and it lives in the setup.
Agreement first, project second
Aligno replaces the vague PDF proposal with a structured scope agreement that both parties sign off on before work begins.
The core workflow is simple. You create a Scope—a structured document that specifies deliverables (with explicit in/out lists), communication rules (who contacts whom, response time expectations), revision limits (with a clear definition of what counts), and approval gates (who signs off on what, and by when).
The Scope is not a contract in the legal sense—it's a shared reference document that both parties have explicitly agreed to. When a question arises mid-project ("is this in scope?"), both parties open Aligno and look at what was agreed. The answer is usually unambiguous. The conversation is short.
Where Aligno goes beyond a document is in the change request flow. When the client wants something that falls outside the agreed scope, they submit a Change Request through Aligno. The agency responds with impact (time, cost). The client approves or declines. The change request becomes part of the project record. No email threads, no ambiguity, no "I thought you said."
The result: fewer disputes, better margins, and clients who are more satisfied because expectations were clear from day one.
Built on proven, boring infrastructure
Aligno is built on a deliberate "boring tech" stack—tools that are mature, well-understood, and unlikely to surprise you in production.
SvelteKit powers the front end. It's fast, SEO-friendly, and produces lean bundles. The UI is optimised for async workflows: agency and client can be in different time zones, working asynchronously on the same Scope document.
Supabase handles the backend: PostgreSQL for data, Row Level Security for multi-tenant data isolation, Auth for user management, and Realtime for live updates when both parties are reviewing a scope simultaneously.
Vercel handles deployment—zero-config, global CDN, automatic preview deployments for every pull request.
The stack is intentionally simple. Aligno is a document and workflow tool; the competitive advantage is in the UX and the opinionated scope structure, not in infrastructure complexity.
In active development
Aligno is in active development. Core features—Scope creation, client sharing, Change Request workflow—are being built and internally tested.
The waitlist is open. Early access users will get a significant discount on the launch pricing, direct access to the founding team for feedback, and input into feature prioritisation.
Target: private beta in Q2 2026, public launch Q3 2026.
From the blog
Get early access
If you run an agency, a studio, or a freelance practice and scope creep is eating your margins—Aligno is being built for you.