Swiftly Workspace ERP is our own product, not a client we are allowed to name. It is a business workspace with native clients for iOS, macOS and tvOS, backed by a Vapor server and PostgreSQL. The card on this site marks it v1.5 and ongoing. That last word is the point of the article. We are extending it. We are not announcing a rewrite, and we are not going to dress a year of work up as an AI miracle.
What the product page actually lists
The published description is a list, and this post keeps it as a list. Inventing a tour of screens we have not described would only make the product sound larger.
- CRM, contracts and projects.
- Invoicing, inventory, sales orders and deliveries.
- Trip planning and timesheets.
- Email, and AI-powered task automation.
The tech line next to that list is Swift, SwiftUI, Vapor, PostgreSQL and Claude. "Claude integration" on the product card is the server, not a claim that every screen is a chat. The four screenshots we publish are specific enough to describe without adding plot.
- A project budget dashboard on the Mac: total projects, total budget, total spend, burn rate, and a status breakdown.
- A draft sales order: the customer, the delivery address, and a financial summary.
- A draft invoice: line items, quantities, unit prices, a discount, tax and totals.
- An email-response task assigned to an AI sales agent, with the agent chat beside the task details.
That fourth screen is the AI reality inside the product, as far as the picture goes. A task exists. It is assigned to an agent. The chat sits next to the task, not instead of it. I will not describe what the agent is allowed to send, because the alt text does not, and a imagined policy would be fiction.
The one number we have already published
A consulting article about custom operations software measured the Workspace repository on 1 October 2026, at the commit from 26 September 2026. Between 2 October 2025 and that commit there were 27,197 commits, and 20,636 of them carry a Claude co-author line. The same article refuses, in the next breath, to make a measured claim about FeedbackKit. This post borrows the Workspace count and keeps the refusal.
A co-author trailer means the trailer is on the commit. It does not mean those commits were written by a model and glanced at by a person, and it does not mean the commits without the trailer were written with the network unplugged. Dividing the two numbers and calling the result a measure of how the ERP was built would be a stunt. We are not doing it. The figure is evidence that the model is in the history of this repository across that year, beside a product that is still a native app and a Vapor server.
The version on the card is 1.5, ongoing. The commits are on that repository, not on a sequel we threw away and started. The rebuild-or-patch article uses this on purpose: when agents joined the history, the product's answer was another version, not a new name.
Native clients, including the odd one
iOS and macOS are the obvious pair for an ERP that a person runs at a desk and checks on a phone. tvOS is on the product card too. This article does not invent a reason for the television client beyond the fact that it ships. A business app with a third Apple platform is still three native clients to review. That is the same trade we describe in the native-or-cross-platform piece: we accepted the review, because the product is ours and the screens are the product.
The invoice screen is not the PDF library. Swiftly-PDFKit draws invoices from a Swift document model and is published separately. Nothing on the Workspace card says the Mac app calls that package. Until we publish the wiring, the two stay unrelated in print. If you want the library, its article is the one. If you want the workspace, the site is swiftly-workspace.com.
What this is not
- Not a customer story. There is no logo wall and no quote.
- Not a claim about revenue, users, or uptime.
- Not a statement that Claude writes the ERP. The co-author count is the statement. The boundary around it stays.
- Not the dedicated-developer offer. That offer is people from Davao joining your codebase. Workspace is a product we own, in our repository, which is why the ownership article uses it as the contrast.
If you are deciding whether to keep extending the system you have, Workspace is the example we can point at without asking a client's permission. It is still being built. The badge says so, and the commit dates say the building did not start last week.
Comments
Loading comments…