{"url":"https://ticulate.com/nick/maestro","live":true,"project":{"slug":"maestro","owner":"Nick","ownerHandle":"nick","name":"Maestro","summary":"A self-hostable platform of purpose-built AI agents that compose into scheduled, multi-step workflows for small businesses.","status":"ontrack","visibility":"public","next":"Get the security and correctness fixes onto the main line — three commits are written and verified but still sit on an unmerged local branch","started":"2026-05-07","target":null,"updated":"13 Aug","updatedAt":"2026-08-13T23:35:42.378Z","done":8,"total":10,"health":null,"logo":null,"links":[{"url":"https://letmaestro.com/","label":"letmaestro.com"},{"url":"https://github.com/mcinnisdev/Maestro","label":"Repository"},{"url":"https://letmaestro.com/changelog","label":"Changelog"},{"url":"https://letmaestro.com/manifesto","label":"Manifesto"}],"purpose":{"why":"The work that grows a small business — finding the right people, writing to them, handling what comes back — is steady, repetitive and rarely done well, because nobody has time for it. General agent platforms answer this with a blank canvas, which hands the operator a building problem on top of the one they already had. Maestro takes the opposite position: it ships the agents already wired for the job and asks you to configure them.","who":"Small businesses doing their own outbound, starting with three closed-beta design partners selling B2B software. They want to own their contact data and run the thing on their own box rather than rent it.","success":"The hero automation books real meetings for the three design partners, running on their own infrastructure, against their own data, with a human approving every message that leaves."}},"features":[{"id":"b2b-saas-outbound","name":"B2B SaaS outbound","area":"Automations","state":"beta","version":"v0.1.0","shipped":"2026-05-07","summary":"The hero automation. It finds people matching your ideal customer, drafts a personal opener for each, sends from your own inbox, reads and classifies the replies, and records every contact and every interaction in a pipeline you own.","detail":"Two graphs: one for outbound, one for reply triage. Both retargetable by editing plain-English instructions — no code change needed to point at a different kind of customer.","review":{"status":"none"},"links":[]},{"id":"review-mode","name":"Review mode","area":"Safety","state":"live","version":null,"shipped":null,"summary":"Nothing reaches a customer without a person approving it. Drafts queue up as cards, you read them, and only then do they send.","detail":"On by default. It is the reason an automation can be trusted with a real inbox.","review":{"status":"none"},"links":[]},{"id":"composer","name":"Composer","area":"Building","state":"live","version":"v0.2.0","shipped":"2026-05-08","summary":"A canvas for building automations. Drag steps on, draw the connections between them, configure each one in place, and save.","detail":"Replaced the configure-only era, where changing an automation meant editing seed data.","review":{"status":"none"},"links":[]},{"id":"orchestras","name":"Scheduled orchestras","area":"Running","state":"live","version":"v0.3.0","shipped":"2026-05-09","summary":"Attach an automation to a schedule and it runs on its own. Every run is recorded step by step, so you can see exactly what happened and what it cost.","detail":null,"review":{"status":"none"},"links":[]},{"id":"pipeline","name":"Built-in pipeline","area":"Data","state":"live","version":null,"shipped":null,"summary":"Contacts and their history live inside Maestro, so there is no CRM to buy before the first automation can run. Everything is exportable.","detail":"Deliberately separate from whatever CRM the business already has. Maestro owns its own record of what it did.","review":{"status":"none"},"links":[]},{"id":"agents","name":"Agent catalog","area":"Building","state":"live","version":null,"shipped":"2026-05-08","summary":"Reusable agent setups — the instructions, the model, and the tools it is allowed to touch — that any automation can point at.","detail":null,"review":{"status":"none"},"links":[]},{"id":"skills","name":"Integrations","area":"Integrations","state":"live","version":"v0.4.1","shipped":null,"summary":"Seven ship in the box: lead search, email, web research, writing, notifications, the pipeline itself, and a general escape hatch for anything else with an API.","detail":"Each one declares what it can do and what credentials it needs, and the runtime finds them at startup.","review":{"status":"none"},"links":[]},{"id":"self-host","name":"Self-hosting","area":"Operations","state":"live","version":null,"shipped":null,"summary":"The whole thing runs on one machine you control, behind your own domain, with no ports open to the internet. Sign-in happens at the edge.","detail":"Docker Compose plus a Cloudflare tunnel. Migrations and first-run setup happen on their own.","review":{"status":"none"},"links":[]},{"id":"conventions","name":"Component conventions","area":"Building","state":"live","version":"v0.4.1","shipped":"2026-05-12","summary":"A written contract for how automations, agents and integrations get authored, in a form both a person and a machine can read — so everything built later is built the same way.","detail":null,"review":{"status":"none"},"links":[]},{"id":"maestro-ai","name":"Describe it and have it built","area":"Building","state":"building","version":null,"shipped":null,"summary":"Say what you want the automation to do and have it drafted for you. The first of four steps is done: the authoring contract, and a single checkable definition of what a valid automation is.","detail":"The next step is an in-browser editor for integrations, bound to the published schema.","review":{"status":"none"},"links":[]}],"roadmap":{"doing":[{"note":"Two dozen findings from a full code review. Roughly two thirds are fixed on a branch; the rest are open.","when":"Now","title":"Harden the platform before the beta widens"}],"planned":[{"note":"Contact import from a spreadsheet, and a read-only billing connection. Two pieces that unblock three automations between them.","title":"Shared groundwork for the next wave of automations"},{"note":"Answer an inbound enquiry within minutes instead of days. Needs no new integration at all, so it is the fastest thing on this list.","title":"Speed to lead"},{"note":"Chase overdue invoices and report the money actually recovered. The most provable automation on the board.","title":"Invoice chaser"},{"note":"Reach lapsed customers, the cheapest revenue a business can get.","title":"Customer win-back"}],"considering":[{"note":"Ask happy customers for a review at the right moment. Opens a whole new kind of customer — local and service businesses.","title":"Review engine"},{"note":"A briefing before every meeting in the calendar. Turns Maestro from a background job into something opened daily.","title":"Meeting prep"},{"note":"Notice when a competitor changes their pricing or their pitch.","title":"Competitor watch"},{"note":"Find what a site could rank for and brief a human to write it. Deliberately does not publish anything itself.","title":"Content opportunities"},{"note":"The written contract and the machine-checkable shape are done. The editor is not.","title":"Describe an automation and have it drafted"}]},"updates":[{"timestamp":"12 Jul","at":"2026-07-12T12:00:00.000Z","statusChange":null,"title":"A crashed worker no longer strands a run, and a schedule fires exactly once","body":"Runs now report they are alive while they work, and anything that stops reporting is closed out rather than sitting as running forever. Schedules claim their slot in a single step, so a restart, a second copy of the service, or a failure part-way through a tick cannot produce the same run twice. Long downtime replays at most one run per schedule instead of a burst.","tags":["reliability"],"links":[]},{"timestamp":"01 Jul","at":"2026-07-01T12:00:00.000Z","statusChange":null,"title":"A full review found two dozen problems worth fixing before the beta widens","body":"A systematic read of the runtime, the API, the integrations and the database turned up twenty-four issues, several of them security-relevant. The most serious were fixable straight away and were: credentials can no longer be read out without authorisation, the general-purpose web step can no longer be pointed at internal addresses, and outgoing mail headers are sanitised. Two thirds of the list is now written and verified, and none of it has shipped yet.","tags":["security","quality"],"links":[]},{"timestamp":"12 May","at":"2026-05-12T12:00:00.000Z","statusChange":null,"title":"A written contract for how everything is built","body":"How an integration, an agent, an automation and a schedule are authored is now written down in a form both a person and a machine can read, and there is a single definition of what makes an automation valid — checked in one place instead of three. This is the groundwork for describing an automation in plain English and having it drafted for you.","tags":["release","foundations"],"links":[]},{"timestamp":"08 May","at":"2026-05-08T12:00:00.000Z","statusChange":null,"title":"Automations become something you build, not just configure","body":"A canvas replaces the old edit-the-seed-data workflow. Steps get dragged on, connections drawn between them, and each step configured where it sits. Changing what an automation does no longer means touching the database.","tags":["composer"],"links":[]},{"timestamp":"07 May","at":"2026-05-07T12:00:00.000Z","statusChange":null,"title":"First dogfood-ready release goes to three design partners","body":"Maestro runs end to end: it finds leads, writes to them from the operator's own inbox, reads what comes back, and keeps its own record of every contact and interaction. Everything a customer would see waits for approval first. Three closed-beta partners are running it on their own machines.","tags":["release"],"links":[]}],"feedback":[]}