Local-first business app In development

The whole business.
One fast app.

Customers, deals, quotes, invoices, calendar, projects, stock and team, in one native app. Your AI agent works inside it through MCP. Automations do the routine work while you do the real work.

  • NativeWritten in Rust. Opens in a blink, scrolls 10,000 rows without a stutter.
  • OfflineYour data is on your machine. It syncs with the team when you are online.
  • Agent-readyAn MCP server is built in. Every tool has a scope, and you approve what matters.
Deals board. The side panel shows what the automations and the agent did on this deal.

One app instead of

MCP server, built in

Your agent runs the back office.
You approve.

Philo speaks the Model Context Protocol. Connect Claude Desktop, Claude Code or any MCP client, and the agent can read your business, draft the work and, with your approval, act on it. Every call shows up live in the Agent panel.

    Scripted demo. Tool names and scopes are the planned MCP interface.

    The agent drafted three reminders. Sending is outside its scope, so it asks.

    On your desktop · claude_desktop_config.json

    {
      "mcpServers": {
        "philo": {
          "command": "philo",
          "args": ["mcp", "--scope", "sales.read,finance.read,email.draft"]
        }
      }
    }

    From anywhere · remote MCP on your hub

    claude mcp add --transport http philo \
      https://hub.olive-oak.example/mcp

    Sign-in with OAuth. You pick the scopes on the consent screen.

    Toolsgrouped by scope
    MCP tools by scope
    sales.readsearch get_contact get_contact_timeline list_deals get_pipeline
    sales.writecreate_contact update_deal move_deal add_note merge_contacts
    finance.readlist_invoices get_cashflow list_expenses vat_summary
    finance.writedraft_quote draft_invoice record_expense match_payment
    workcreate_task list_projects log_time get_calendar find_free_slot
    email.draftdraft_emails list_email_templates summarize_thread
    stocklist_products get_stock draft_purchase_order list_low_stock
    automatelist_automations draft_automation test_automation get_runs
    reportsrun_report get_metric sql_readonly
    always askssend_emails send_quote issue_invoice refund delete_* enable_automation
    • Scopes per client. A client sees only the scopes you gave it. Payroll and bank stay closed unless you open them.
    • Approval for the outside world. Sending, issuing, refunding, deleting and switching on automations wait for a person.
    • Drafts first. The agent writes quotes, invoices and emails as drafts. You see the diff before anything is final.
    • Audit log. Each call is stored with its client, arguments and result. One click undoes a write.
    • Local by default. The desktop server listens on 127.0.0.1 with a random token. Remote MCP is off until you turn it on.
    • Your data, your model. Philo sends nothing to an AI service. Your client talks to its own model.

    Automations

    Say it once.
    It runs every day.

    An automation is a short rule: when something happens, check a condition, do the work. Rules run on your hub, so they fire at 3 a.m. with every laptop closed. Build them by hand, or describe one in a sentence and let the agent draft it.

    Overdue follow-up. Average lateness went from 13 days to 4.
    When

    A record changes, a time arrives, or the outside world calls in: a booking, a form, an email, a Stripe payment, a webhook.

    Only if

    Filters on any field, tag, owner, amount or custom field. Combine with and, or, not.

    Do

    Create, update, email, SMS, task, invoice, move a deal, call a webhook. Steps run in order and can branch.

    Wait

    For a time, a date field, or an event, such as “until paid”. Waiting runs survive restarts.

    Ask the agent

    A step that hands the context to your agent: draft a reply, classify an email, pick a slot. Its output is a draft that waits for approval.

    Recipes that ship with the app

    Booking made

    Booking → lead

    Create the contact and a deal in Lead, send the confirmation, add the visit prep checklist.

    Quote accepted

    Quote → project

    Move the deal to Won, issue the deposit invoice, start the project from a template, tell the team.

    Invoice 7 days late

    Polite chase

    Reminder with a payment link. Still unpaid after 5 days: a personal draft and a call task.

    Email received

    Inbox triage

    The agent tags the email as lead, support or invoice, files it on the right contact and opens a ticket when needed.

    Stock below minimum

    Reorder

    Draft a purchase order to the usual supplier with the usual quantity. You approve and it goes out.

    No reply in 3 days

    Follow-up

    A gentle follow-up on a sent quote. Stops by itself when the client opens or answers.

    Every Monday 08:00

    Week brief

    The agent writes the week: meetings, deals to push, money due in and out. It lands in your inbox.

    Month end

    Accountant pack

    Invoices, expenses, receipts, VAT summary and payroll prep in one export, sent to your accountant.

    From a sentence

    “When a quote has been open for a week and the client looked at it, remind me to call them.”

    draft_automation → When quote.age = 7 days · Only if quote.viewed and not quote.accepted · Do create_task(owner, "Call about {quote}") · draft

    The agent drafts. Test runs the rule on a real record without side effects. You switch it on.

    • Test before on. A dry run shows each step on a real record and sends nothing.
    • History. Every run is kept with its steps, waits and errors. Retry a failed step from the list.
    • Loop guard. A rule cannot trigger itself in a loop. Limits per hour stop runaway sends.
    • Webhooks both ways. Call out to any URL, or receive calls on a signed endpoint. n8n and Zapier still work if you need them.

    A look around

    Everything about a client,
    on one screen.

    Email, calls, bookings, payments, files and agent notes in one timeline. Filter by kind.

    All features

    Turn on what you need.
    Leave the rest off.

    Each module is a switch per workspace. A bakery turns on booking, stock and the shop. A design studio turns on quotes, projects and timesheets. Same app.

    Customers and sales

    • Contacts and companies with tags, custom fields, logos and duplicate merge
    • Deal pipeline as a board or a list, with your own stages
    • Timeline of every email, call, note, file, payment and booking
    • Quotes from the catalog, accepted online
    • Email capture by forward or BCC
    • Import and export CSV, with a mapping step
    • Search across everything, instant and offline

    Money

    • Invoices with VAT, yearly numbering, PDF, credit notes and recurring invoices
    • Payment links and card payments with Stripe
    • Expenses from a photo of the receipt
    • Bank statement import and automatic matching
    • Accountant export with a VAT summary, and Greek myDATA
    • Subscriptions and memberships, with MRR

    Time and work

    • Calendar for the team, synced with Google and CalDAV
    • Booking page with buffers, deposits and reminders
    • Tasks with owners, due dates and checklists
    • Projects with milestones, a board and client progress in the portal
    • Timesheets with a timer. Billable time goes on the invoice
    • Tickets from email and the portal, with SLAs and canned replies
    • Forms for the website: leads, intake, surveys

    Communication

    • Inbox: connect a mailbox, read and send from the contact page
    • Templates with fields from the record
    • Campaigns to segments, with consent and unsubscribe
    • SMS and WhatsApp reminders
    • Call log and click to call
    • Client portal: quotes, invoices, documents, project status, uploads

    Products and stock

    • Catalog of products and services, with prices and VAT rates
    • Inventory per location, with low-stock alerts
    • Orders and delivery notes
    • Suppliers, purchase orders and goods in
    • Shop: a simple order page with checkout
    • Point of sale on a tablet

    Team

    • Members and roles, with permissions per module
    • Leave requests and a leave calendar
    • Shifts, clock in and clock out
    • Payroll prep: hours, overtime and leave, exported for your accountant
    • Contracts from templates, signed in the portal

    Agent and automation

    • MCP server, local and remote, with scopes
    • Approvals for every action that leaves the building
    • Automations with triggers, conditions, waits and branches
    • Ask-the-agent steps inside automations
    • Webhooks in and out, and a public API
    • Audit log with undo

    Insight

    • Dashboard you build from a metric catalog
    • Reports: sales, revenue, unpaid, time per project
    • Saved views, per person or shared
    • Export to CSV and PDF

    Your data

    • Local-first: a full copy on each desktop, offline ready
    • Sync through your hub, live between team members
    • One file per workspace, SQLite, yours to keep
    • Backups before each update, and a download any time
    • English and Greek, more to follow

    How it works

    Fast on your desk.
    Open to your clients.

    Desktops sync with the hub. The hub serves clients, outside services and the remote MCP endpoint. Desktop · ChristinaRust · local SQLite Desktop · Alexworks offline AI clientMCP · stdio Hubsync · automationsportal · bookingwebhooks · MCP Clientsportal, booking, forms ServicesStripe, bank, email Remote agentsMCP over HTTPS

    The desktop app

    A native Rust app for Linux, Windows and macOS. Each workspace is a SQLite file on your disk. Lists, search and reports run locally, so they are instant and they work on a plane.

    The hub

    A small Rust server. It syncs the team, runs automations on time, serves the client portal and booking page, and takes calls from Stripe, your bank and your mail. Use ours, or run it on your own box with one Docker image.

    The agent

    On the desktop, the app is an MCP server for local clients. On the hub, the same tools are available over HTTPS with OAuth, for agents on the web or on a phone.

    FAQ

    Asked first

    Do I need an AI subscription?

    No. The app, the automations and every module work without an agent. The agent is an extra that you connect when you want it.

    Which AI clients work?

    Any client that speaks MCP: Claude Desktop, Claude Code and others. The local server uses stdio. The hub serves streamable HTTP with OAuth.

    Can the agent send email or money on its own?

    Only if you allow it. By default, sending, issuing, refunding, deleting and switching on automations wait for a person to approve. Each approval is in the audit log.

    Does Philo send my data to an AI company?

    No. Philo has no model of its own. Your MCP client reads what its scopes allow, and that client talks to the model you chose.

    What happens when I am offline?

    You keep working on your local copy. Changes sync when you are back. Automations and the portal keep running on the hub.

    Can I host it myself?

    Yes. The hub is one Docker image with one data folder. Each workspace stays a SQLite file you can copy.

    Can I bring my data from another CRM?

    Yes. Import contacts, companies, deals and invoices from CSV, with a mapping step and a duplicate check.

    Is it ready?

    Philo is in development. The current web version runs contacts, deals, tasks, Stripe and the client portal. The desktop app and the modules on this page come next. Early access members get each part first.

    Early access

    Run your business
    from one window.

    We open Philo to small teams in waves. Tell us what your business does and which tools you want to drop.

    Ask for early access

    support@cgeosoft.com