The August–September development journal, collected September 15. What changed, and why we built it that way.
Our new Agents page previews a marketplace built around recognizable jobs, from a newsletter editor to a project coordinator.
The Social launch work starts with one idea and gives each destination its own version, review, and result.
A conversation can start the work. Tickets gives it an owner, a place, and a visible finish.
An Amo’s computer now has a richer working life: shared or individual machines, continuing tasks, and a pace you can choose.
A teammate, client, vendor, or contact can all belong to the same business story. People gives them a common home.
Work arrives in bursts. The Feed brings activity into one readable stream, with the things that need you kept close.
The Mac companion gives ongoing work a quiet presence beside the windows you already use.
The menu bar and Dynamic Island offer a different kind of interface: enough information to decide whether to open the app.
Shape, color, name, and a clear job make an agent easier to find. Its identity should follow it into the next conversation.
The iPhone app begins with your Amos. That changes what a quick visit to your business can feel like.
A client question can cross a proposal, a project, and an invoice. Retrieval has to follow the business across those boundaries.
Files, documents, forms, and templates belong together. Finding the work should be the beginning of doing it.
An assistant that remembers your preferences also needs a way to be told that they have changed.
A screenshot, a brief, a spreadsheet: the work usually arrives with something attached. Those details deserve to survive the conversation.
A command-line client for Amolfi: sign-in with a code and a browser confirm, runs you can start, follow, steer and cancel, and an approval that stays with a person in the app.
Why metering the work performed is the honest way to price AI software, and why the meter should read the same whether the work came from the app, a terminal, or your own code.
Amolfi’s public API is live at api.amolfi.com: your real records, governed runs, and signed webhooks, with a permission ceiling that lets a machine propose and never approve.
Amo can now open a browser of its own to do the web legwork a task needs, and you can watch every session as it works.
Hand Amo a list and it splits into a session per task, all running at once, all still waiting on you to sign off.
One idea in, a channel-shaped draft out for every surface you publish on, with your approval standing between the drafts and the world.
What a phone call has to prove before it can reach your workspace: caller ID is a hint at the door, so reading and answering ride the call while money and anything outbound becomes an owner-approval card waiting in the app.
One editor for docs, slides, and sheets, with AI that pulls its numbers from your real records and cites where each one came from.
Questions answer instantly, low-risk writes follow the setting you chose, money and anything leaving the workspace waits for an owner’s approval, and every run leaves a record of who asked.
Dozens of live collections moved from Firestore to Aurora, one small wave at a time behind a single signed gateway, with the numbers checked before any old path was retired.
The landing page walks the product domain by domain, in the same order the software itself is arranged.
Your connected bank balance now sits alongside quotes, invoices, and retainers inside Finance.
App data now runs on one AWS data spine with live subscriptions, so screens update on their own and there is nothing to sync between silos.
Failed webhook deliveries now retry on a widening 1s, 4s, 16s schedule, and every attempt is logged.
One engine runs an agency and a cabinet shop without branching, because each trade’s vocabulary arrives as data layered over a shared base.
Forms, approvals, signing, booking, client portals: every link you send outside your workspace can do exactly one thing, and nothing else.
Your whole business as one explorable map, and the same graph your agents think with.
Write once, get a version built for each channel, and publish from one screen, with every post waiting on a human’s approval.
Describe your buyer, and the Lead Factory finds, enriches, and routes leads into the pipeline as tracked records inside your CRM.
AI operators under domain Chairs, each with a hard ceiling and a kill switch, and money or outbound work that always waits for an owner.
Amolfi records money the day it actually moves, which is how owners already keep score.
Row-level security plus a transaction-local org id, so the database refuses another tenant’s rows even when the application asks for them.
Intake, tasks, deliverables and approvals on one board, so work stops disappearing in the gaps between tools.
One customer record carrying contacts, deals, files and history, so the CRM knows the invoice and the project, not just the pipeline.
Your CRM has never seen an invoice. The case for running a company on one layer with one shared memory.
What Amolfi is, why it exists, and the client-services company it was built inside.