MateOS
MateOS is the internal workspace built for Mate Code Studio. It keeps research, client records, follow-ups, delivery capacity, invoices and recurring operational tasks in one place, so the work that needs attention is easier to see.
MateOS · Dashboard
The project
Running a small studio still creates a lot to keep track of: businesses to research, conversations to remember, follow-ups to complete, projects to deliver, invoices to watch and available capacity to understand.
Generic CRMs can cover parts of that work, but I would still be moving between sales tools, inboxes, project notes and spreadsheets. MateOS started with a simpler question: what do I need in one place to run Mate Code Studio day to day?
The challenge
The problem is usually a collection of small misses: a business that never gets reviewed, a follow-up that slips, a project that becomes overloaded, an invoice that needs attention or a conversation that has to be reconstructed from memory.
The goal
It needed enough structure to support daily work without turning into a miniature enterprise platform.
The solution
MateOS connects business research, CRM records, follow-ups, active projects, capacity planning, payment visibility and recurring operational actions in one place.
The point is not to have more modules. It is to keep the context from one stage of work available when the next stage begins.
A deliberate decision
The dashboard is not there to fill the screen with charts. It brings together the work, money and relationships that may need attention, with the relevant action close by.
Projects at risk, cash due, follow-ups, overdue actions, client messages, active work and businesses waiting for review are more useful to me than vanity metrics.
The same idea carries through the rest of MateOS: keep related information together and reduce the time spent working out what happened before.
What was built
Each area exists because it solves a recurring part of the work. MateOS is not trying to reproduce a generic CRM feature-for-feature.
Today, overdue work, project risk, cashflow signals, messages and review queues are surfaced in one action-oriented starting point.
Potential businesses can be researched in selected markets and kept separate from the CRM until they are worth reviewing further.
Research can be filtered and reviewed before a business becomes an active CRM record, keeping early-stage information separate from real client relationships.
Prospects, leads, clients and past clients stay searchable with business context, lifecycle status and contact policy in one place.
Weekly allocation, deadlines and a six-month availability view help protect delivery capacity before new work is committed.
Deterministic rules can create actions around events such as opportunity wins, waiting on clients, invoice reminders and payment chasing.
Workflow
MateOS follows the same basic path I use in the business: research a potential company, review it, move relevant relationships into the CRM, keep the next action visible and plan delivery once work becomes real.
Inside MateOS
These six views show the parts of the system I use for daily priorities, research, client management, delivery planning and recurring admin.
The dashboard brings together delivery risk, cashflow, follow-ups, overdue actions, messages, active projects and businesses waiting for review in one place.
Research can be collected by market and location, then reviewed separately instead of being mixed straight into active client records.
The review queue keeps prioritisation and service-fit notes together before a business progresses into the CRM.
Search, lifecycle filters and contact controls keep business context usable across prospects, leads, clients, past clients and archived records without splitting the relationship across separate tools.
Monthly capacity, weekly allocation, deadlines and a six-month forward view make availability visible before more work is committed.
Configurable rules turn clear business events into predictable actions, including opportunity wins, waiting on clients, invoice reminders and payment chasing.
Built with constraints
MateOS is built for one operating environment: Mate Code Studio. Features are added because they solve a recurring operational problem, not because a generic CRM is expected to have them.
Research and discovery are separate from the core CRM. If new work comes through referrals, website enquiries or manual research, the rest of MateOS still works in the same way.
That keeps the MVP useful now and leaves room to add finance, delivery or automation features when daily use proves they are worth having.
The outcome
MateOS is not a SaaS product or a promise of automated growth. It is a working internal tool that gives me one place to understand relationships, see what needs attention and keep delivery organised.
Need an internal tool?
If important work is spread across spreadsheets, inboxes and generic tools, a focused internal system can put the information and next actions in one place.