com1 · Features · what $24 a month buys

Projects, tickets and milestones

Every client request becomes a ticket in that client's project, with a milestone and a status your team defined. Star the projects you work in most and they lead your list.

01 Tickets and custom statuses Statuses per project, each with automation: complete the ticket, clear fields, or assign it to a person, the creator or the project owner.

Fig. 1 — a project's tickets
02 Board, swimlane and Gantt The same tickets as a list, as lanes per milestone, or on a timeline with start and due dates.

Fig. 2 — the swimlane view
03 Milestones and the Gantt Group tickets toward a deliverable and read the dates across milestones; both dates stay mandatory when the team wants them.

Fig. 3 — the Gantt
04 Products and releases Platforms, environments and semver versions per product; a GitHub release becomes a version, named after its tag.

Fig. 4 — a product sheet
05 Priorities and triage Low, normal, high or urgent on every ticket, with a priority filter and order on the board and the ticket report. With an AI add-on, Claude reads each new ticket and sets a second priority beside the author's, seen only by the project roles you allow, and plans the start and due date of a quick ticket from the apps.
06 Comments and @mentions Discuss on the ticket and correct your own comments afterwards, marked as edited; a mention notifies and subscribes the member and is highlighted in the thread.
07 Recurring tickets Daily, weekly, monthly, quarterly or yearly, with a lead time that surfaces them before the due date.
08 Files, Loom and screen recordings Drop files on a ticket, paste a Loom link, or record the screen from the Mac app (⌘⇧R) and attach it. Coming next: record a meeting on the Mac or iPhone and add it to the ticket's Recordings card, where it plays as audio. A meeting recorded on the Mac keeps your microphone and the call as separate tracks: listen to both together, or to one side alone.
09 Notifications and the morning briefing In-app and email for assignments, comments, due dates and payments; a briefing rounds up the day, the Mac app shows banners, and the iPhone app pushes within the hours you set.
10 Needs a hand Beside every page, slips for tickets without an assignee, overdue work, draft invoices, waiting estimates, claims and failed deploys.
11 Subscriber nudges and backlog trend One click reminds a subscriber, throttled to one a day; the dashboard charts open tickets over 90 days.

Estimates, invoices and claims

From the estimate to the paid invoice without leaving the sheet; the PDF is the same one the free generator makes.

01 Invoices Line items, section headers, allowances and charges; one house email letter with per-client departures and a live preview.

Fig. 5 — an invoice
02 Estimates Send an estimate, and when it is accepted it becomes the invoice and the project.

Fig. 6 — an estimate
03 Expense claims Receipts and bank-statement proof grouped into a report, exported as a PDF and a ZIP of every attachment.

Fig. 7 — an expense claim
04 Payments Record payments against invoices; track conversions and account transfers.
05 Invoice payment report What is outstanding per currency, what is overdue, and how long clients actually take to pay, invoice by invoice.
06 Recurring invoices and reminders Monthly or yearly drafts from a template or from time logs, waiting for review; reminder schedules per client at 7, 14 and 30 days.
07 Currencies and tax Any currency; SST, GST, VAT or custom rates per corporation; a received-payments report per financial year with CSV.
08 Items and payment terms Reusable products, services and terms that fill new invoices in.
09 MyInvois Issued invoices signed and sent to LHDN, the QR code on the PDF, and every refusal on one register to fix and resend, on both plans.

Hours

A timer runs on the ticket while the work happens; the minutes are billable the moment they stop.

01 Timers and time logs Start the timer on the ticket; the log carries a description and a date and imports straight into an invoice.

Fig. 8 — the timer on a ticket
02 The project's time logs Every log and every uncommitted timer of a project on one sheet, so nothing runs on or goes unbilled.

Fig. 9 — a project's time logs
03 Hourly rates Rates per project, one as the timer default, others derived by factor; applied when the invoice is made.
04 Billing targets and the heatmap A monthly target, the hours against it on the dashboard, and an activity heatmap of when the work happens.
05 Estimates and working time Every ticket can carry an estimate, typed as 1h30 or 2.5; a team may require one. The team sets its working week and hours, its holidays, each person's time off and a part-timer's own hours.
06 Workload com1 Platform One row per person, one column per day: the estimated work left on their tickets, spread over their working days, against the hours they have. Free hours in the plain, hours over in red, the tickets that will not fit before their due date called out, and what the totals leave out listed underneath.

Contacts, corporations and deals

The client is a corporation with contacts; the opportunity is a deal on a pipeline; both keep their own timeline.

01 Deals and the pipeline Lead, qualified, proposal, negotiation, won, lost; the deal page holds its stakeholders, estimates and timeline.

Fig. 10 — a deal
02 Contacts and corporations Contact details linked to the corporation, its projects and its invoices; every email and call on the timeline.
03 Calls and notes ⌘J logs a call from any page onto the contact's timeline and refreshes the last interaction.
04 Tags, segments and saved filters Tag contacts and deals, filter by one or many, and keep the filters you use as presets.
05 Stakeholders and last interaction Every person on a deal, and the date you last spoke to each contact, sorted oldest first.
06 Deal to estimate to invoice Estimates on the deal page, created in one click, so the pipeline runs through to the invoice.
07 Custom fields com1 Platform Text, number, date or select fields on contacts and deals for what your team records.
08 Lead scoring com1 Platform Rules such as "reached proposal, +15" score contacts and deals; daily decay cools stale rows.
09 Birthdays and banks A birthday calendar with a morning reminder; banks, branches and accounts for payment tracking.

The whole team, one price

Owners, members and external seats for contractors and client stakeholders, at no charge per person.

01 Roles per project Owner, member or viewer on each project; a member sees the projects they are on.
02 Virtual members Contractors and stakeholders as members without a login; assign them tickets, send them nothing.
03 Features on and off Switch off what the team does not use — estimates and workload, deals, expense claims, notes — and it leaves every menu and page, for everyone. The data stays for when it is switched back on.

04 Custom roles com1 Platform Roles with the permissions your agency needs, per feature.
05 Project-level access com1 Platform Who can open which project, independently of their team role.

Hosting and deployment com1 Platform

On com1 Platform the same project holds the client's servers and containers, in your own AWS account.

01 Servers EC2 instances on RHEL 10 and Graviton, run by your clusters and managed over SSM; CPU, memory, disk and heartbeat alerts by email or Telegram.
02 Containers Podman under systemd Quadlets: env, ports, volumes, healthchecks and limits.
03 Clusters A cluster brings its own load balancer and runs between a minimum and a maximum of RHEL 10 servers, from a single one up to ten, on the hourly licence or your own Red Hat subscription. An Auto Scaling group keeps the number you ask for; when a server dies it is replaced, set up and deployed with your projects before it gets traffic. A deploy rolls through the servers one at a time: each leaves the load balancer, is deployed, and must pass its health check before the next one goes. Your certificates move to the load balancer as they are. Connect your own Cloudflare account and the cluster's page lists what each domain needs there: verified through Cloudflare, a Cloudflare Origin Certificate issued for it, and its DNS pointed at the load balancer. You confirm the list; com1 moves DNS only once the servers serve the domain, and leaves alone any record that changed in the meantime. Optionally it scales on CPU, and its page charts every server's CPU, memory and disk side by side. Your RDS databases connect to it, and the S3 buckets a project uses are made reachable from the cluster's servers automatically. The projects are the ones you already run: move one in from its page, and com1 does the rest in one confirmed run. It copies the registry login, connects the project's database, deploys the cluster one server at a time and checks the site through the load balancer before switching its DNS in Cloudflare. If anything fails first, the project moves back and visitors never notice.
04 Deploy hooks GitHub Actions calls com1 with a short-lived OIDC token once the image is pushed; no secret to store. You hear when the release is live, or when it fails.
05 A terminal into any container Run a command in a running container from the sheet and read the output live.

06 Memory allocator Drag a server's RAM across projects and containers; see the OS reserve and the free pool. A cluster's split is set once on its page and holds on every server it runs.
07 Domains, SSL, databases and backups Root domains verified once with a TXT record, which com1 adds itself when your connected Cloudflare account holds the zone, with their subdomains added under them; wildcard SSL, RDS and Aurora databases, S3 buckets, SQL import and scheduled backups.
08 Backups that tell you when they stop A failed run shows its reason on the config, on the stack and in the needs-a-hand pad; a run that never started is caught too, and the team owner is emailed either way.
09 SSH keys Team-level keys deployed to a server; the last key removed closes SSH.
10 A private Composer registry The Composer packages add-on, on either plan: CI publishes a tag with an API key, your servers install with pull tokens that can only read, and every pull is counted per version, per token and per day. One line in composer.json, one in auth.json; packagist.org stays for everything else.

What com1 connects to

The mailboxes, the bank and the tools a client already uses, joined to the same records.

01 Email Any number of mailboxes, shared or private: Gmail and Google Workspace by signing in with Google, labels and all, or any IMAP server. Senders are matched to contacts, corporations and deals. Mail arrives as a day's traffic, a register per date; file a message to a client, project, ticket, estimate or invoice, or turn it into a ticket in one click. Read and unread stay in step with your own mail client, and inbox rules keep the noise out: match a sender or subject, or write a rule in your own words and let a model you pick read each mail against it, with every decision logged and undoable.
02 Wise Statements sync hourly into a review inbox; one click turns a line into a payment, a conversion or a transfer, matched to its invoice.
03 Asana Named connections per client workspace; open a new ticket from any Asana task, with its description, comments and attachments.

04 Claude over MCP One connection covers the teams you approve, and every call names the team it acts in. Claude Desktop or Claude Code reads projects, tickets, invoices, estimates and hosting, creates, estimates and updates tickets (never one due today for someone whose working day is already over), checks who has room before it assigns, writes, orders and discounts the lines of draft invoices and estimates from your item catalogue, reads the email you can see (a date range of senders and subjects, then the letters and attachments it needs, with reading mail as its own permission), and deploys only with its own permission.
05 The Mac and iPhone apps On the Mac, a menu-bar companion with search, timers, call notes, screen recording and notifications. On the iPhone, on the App Store now: your unfiled mail as a deck to swipe through, the morning briefing, search, call notes, a quick ticket (just a project, a title and a line, filed with the project's own defaults) and pushes that keep to the hours you set. Coming next on both: meeting recording, with the room's audio added to a ticket.
06 AI, later AI add-ons are bought from the plan sheet: credits for automatic ticket triage and AI email rules. Nothing on the card depends on them.

Compliance and privacy

Malaysian e-invoicing on one side, PDPA on the other, on both plans.

01 MyInvois and certificates Digital certificates with expiry tracking sign every e-invoice; each submission and LHDN answer is kept as an audit trail.
02 Account closure and consent Self-service closure that scrubs personal data and keeps statutory records seven years; per-purpose consent with an audit row for every change.
03 Data export One request returns every record as a JSON manifest plus the original files.
04 Encryption and two-factor Emails, phone numbers and tax IDs encrypted with AES-256-GCM before the database; TOTP with recovery codes and lockout.

05 Audit trail Every cross-team read of personal data by support is logged and visible on your compliance dashboard.
06 Data held in Malaysia Compute, database, storage and registry in AWS ap-southeast-5; transactional email leaves through Singapore and keeps nothing.
07 Retention Old tokens and seven-year-old records pruned nightly, unless you keep them forever.

Notes, search and the dark mode

Notes with a rich editor, a call note from anywhere, and search by meaning.

01 Notes Headings, lists, links and images; a note links to its contact, deal, project or ticket.

Fig. 11 — a note
02 Unsaved text survives What you type in a ticket, comment, note or post is kept as a draft and comes back after a reload, a dropped connection or an update.
03 Call notes from anywhere ⌘J opens a note mid-call without leaving the page; it lands on the caller's timeline.
04 Encrypted notes Stored as ciphertext, excluded from search and never sent to any AI feature.
05 Semantic search Find things by meaning across every record, from the board (/).
06 Nightshade A dark mode in deep blue-grey that follows the system or a toggle.

A business card for every member

A public page at com1.app/cards/company/name, shared by QR, NFC or link.

01 The card Name, title, bio, email, phone, website and social links on a page that reads on a phone.
02 QR and NFC A QR code for print, and a URL for an NFC tag.
03 Save contact One tap downloads a vCard into the visitor's contacts.

04 Templates Default, or Linen; more later.
05 The card's blog Posts with rich text and inline images at the card's own URL.

Prices

com1 · everything above but the hosting section · 25 GB $24 a month
com1 Platform · every line above, hosting included · 100 GB $69 a month

Users, clients, projects, tickets and invoices are unlimited on both. The full rate card

Run the next job in com1 — no card needed

What $24 a month buys and what $69 adds