Write your studio’s framework once and start every client from it. Each deliverable gets a spec with Out of Scope, and each sign-off is a named version you can open a year later.
Free for macOS, Windows, and Linux. No account, no subscription.
Sound familiar?
The statement of work is signed. The real scope moves in calls, emails, and tickets.
Every small extra made sense on the call. Together they ate the margin, and nobody agrees what was in scope.
Five people at the client ask for changes, and nobody has the final say. The answer is in an email thread, or in someone’s head.
Each project copies last year’s template, which drifts every time. People moving between clients relearn the structure, and so does every agent session.
How it fits
Shape the software framework into your studio’s own: the frames your brief needs, the sections every spec must have, your roles. Every new client project starts from it, in that client’s repository.
What you will use most
Your studio’s collections, templates, properties, and roles, installed into each new client project in one click or command.
Record a version naming the commit the client approved, tagged in the repository. When the question comes back, open the project as it was then.
A question about a criterion is a thread on that criterion, not an email. Close it when it’s answered. It stays in the file.
Tasks on a board, each naming its spec, exported to CSV or Excel for the client report.
A new developer, or their coding agent, reads the specs instead of a month of email.
What the client signed off
When the client approves, record a version: a name for that commit, with a tag if you want one. The proposal, phase one, and each change request become rows you can point to. The check tells you if a tag ever moves off its commit.
eidos git version recordOne framework, every client
Keep the framework in your own repository and install it from there into each client project. Or start from the last client’s setup, without its content. To share it, open a pull request to the Registry on GitHub with one manifest pointing at a tagged project. Anyone can then install it as @your-studio/name.
$ eidos install your-studio/delivery@v3 --path framework
$ eidos install ../northwind/Blueprints --setup-only
$ eidos install @your-studio/deliveryStart here
Frames for the brief and specs for the deliverables, with Out of Scope in every template. Shape it in Framework Settings until it fits your studio, and every client after that starts from it.
An app, a service, or a system
Frames for architecture, audience, criteria, and market, and specs grouped by domain.
$ eidos install @BuildableWorks/softwareIn the app: New Project, then pick it from the list.
Download Eidos MD, shape the software framework into your studio’s, and record the first sign-off as a version.
Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.