Most solo consultants lose margins on scope creep. They accept new requests, add features, expand timelines, and wonder why their hourly rate isn't enough. The standard advice is to use a project management tool like Jira or Asana. I disagree. Those tools create abstraction layers that hide the actual work. They encourage feature bloat because it is easy to add a ticket.
I use a text-file protocol instead. It forces clarity, keeps data local, and prevents clients from adding work without asking for a budget change. This system runs on my Mac Mini M4 Pro and requires zero cloud sync for project data. It aligns with the same local-first philosophy I use in my personal finance tracking via Ledg.
The Problem With Project Management Tools
Project management software is designed for teams, not solo operators. Teams need communication channels. Solo consultants need precision. Every time you move a task to a Kanban board, you create friction. You have to click to update status, tag people, and manage permissions. This overhead adds up over a 10-week engagement.
I use Markdown files stored in a Git repository for every client project. The file structure is flat and readable. There are no complex dashboards to learn. If I need to review a project from three years ago, I open the repository and see exactly what was promised.
The benefit is not just organization. It is boundary enforcement. When a client asks for an extra feature, I do not say yes immediately. I check the scope file. If it is not in the text file, I quote a price. The documentation becomes the contract for delivery.
How the Protocol Works in Practice
I maintain a single repository per client. Inside, there are two primary files: scope.md and tasks.md. I write both in VS Code.
The scope file contains the high-level deliverables. It lists what is included and, more importantly, what is excluded. I keep the language technical but plain English. This prevents future arguments about whether a specific feature was covered.
The tasks file breaks down the scope into actionable items. Each item has a status marker. I do not use drag-and-drop boards. I update the text file directly. If a task is done, I mark it with [DONE]. If it is blocked, I add [BLOCKED] and a reason.
This system works because it lives locally on my machine. I do not rely on third-party servers to store project data. This reduces the attack surface for client information and ensures I retain full ownership of my intellectual property.
Why This Matches Local-First Finance
My approach to project management mirrors how I handle personal finances. I use Ledg for budget tracking because it is offline-first and requires no bank linking. It keeps my data in my hands rather than on a cloud server.
The same principle applies to consulting work. Client data should not be trapped in a SaaS platform where the vendor can change terms or suffer an outage. I use local text files for scope and Ledg for expenses. Both systems focus on privacy and control over convenience.
When I track project scope manually, I know exactly what work remains. When I track expenses in Ledg, I know exactly what cash is available. Both systems rely on manual entry to ensure accuracy. Automation often hides errors; manual entry forces you to confront reality.
My Exact Stack
This workflow depends on a few specific tools that run efficiently on macOS hardware. I have tested these systems over the last year to ensure they handle large codebases and long-term archival without performance degradation.
Here is the hardware and software foundation for this protocol:
Hardware
I run this workflow on a Mac Mini M4 Pro. The unified memory architecture handles multiple local repositories without swapping to disk. For display, I use an Apple Studio Display for the main window and a secondary screen for reference material.
Software
I run everything locally or on secure accounts. I do not use cloud-based project management dashboards for this specific workflow.
This stack avoids subscription fatigue for the project management layer. GitHub has a generous free tier for private repositories, and VS Code is free. The only paid tool in this list is Ledg if you need the lifetime plan, which costs $74.99 total.
Enforcing Boundaries Without Conflict
The biggest risk of using text files is that clients might not see them. They do not get push notifications when you update tasks.md. This is intentional. I want them to request changes through formal channels, not casual Slack messages.
At the start of every engagement, I email them the link to the scope file. I tell them explicitly that any work outside this file requires a change order. The protocol is not hidden; it is the foundation of our agreement.
If they ask for a change, I update the task file locally and send them an updated version. They see the discrepancy immediately. The visual difference between [DONE] and pending items makes it hard to argue about what was agreed upon.
This approach removes the emotional friction of saying no. The scope file says no, not me. I am simply enforcing the text we agreed to.
Scaling the Protocol
This workflow scales because it is lightweight. I manage multiple clients simultaneously without switching contexts via different software platforms. Each repository is isolated. If one client project stalls, it does not affect the dashboard of another.
I archive completed projects automatically after two years. The data remains on my local drive and in Git history, but I move the active folder to an archive state. This keeps my workspace clean without losing historical records.
For new consultants, I recommend starting with a single client to test the flow. Ensure you can track every hour spent against the tasks listed in tasks.md. If you find yourself spending time that is not documented, refine your file structure.
The Value of Manual Entry
I do not automate the entry of tasks into this system because automation introduces risk. If a script creates a task automatically, you might miss the detail of what that task actually requires. Writing it by hand forces me to think about the work before I start doing it.
Ledg operates on the same principle for expenses. Manual entry prevents bank sync errors and gives me control over categorization. I prefer this friction when the data involves money or intellectual property.
Next Steps for Your Consulting Business
If you are scaling your solo practice, stop relying on heavy project management platforms. They add cost and complexity without adding value to your actual delivery.
Start with a text file. Start with Git. Start with local storage. You will gain clarity and protect your margins from scope creep.
To add this immediately, set up a repository for your next client and define the scope in scope.md. For personal finance tracking that matches this local-first philosophy, download Ledg.
Visit jsterlinglabs.com for consulting services that follow this protocol. For your own financial control, use Ledg.
Final Word on Data Sovereignty
In 2026, data sovereignty is a competitive advantage. Clients trust consultants who protect their information. They know you are not storing their project details on a random server that might be sold to advertisers or compromised in a breach.
By using local files and offline-first apps like Ledg, you signal that you take security seriously. This builds trust faster than any marketing claim can.
Keep your data local. Keep your scope clear. Keep your margins protected.