Zorderz is open source field service management software for WordPress. Most businesses are already using good tools, and Zorderz is designed to connect those tools so they can talk to each other. Zorderz is an online hub that connects the tools and services your business is already paying for and puts them inside an app your team actually wants to use.
Out of the box, Zorderz is a blank slate
Here is where this is headed. If you already run a CRM and invoicing software, Zorderz should be able to read what is in them and build the matching structure inside your own installation, automatically-ish, so the customers, products and services you already have come across with the same names on both sides and everything knows what to call everything else. Think of it as handing Zorderz the Cliff’s Notes on your business by letting it reach the APIs you connect to it. From there it can work out what your business is and which parts need naming.
To be clear about what is real: that is me describing the future. It does not do that today. It is what we are building toward, and the premise matters more than the timeline. Zorderz is meant to work with whatever you already have rather than replace it, so there is no separate setup ritual by design. A field service management platform should meet your business where it is.
If you do not have those systems, that is fine too. No invoicing software yet? Okay. No CRM? Okay. We are not building our own invoicing or CRM inside Zorderz, at least not yet, because WordPress is not the right place to handle those. But the apps we are building into the platform, like the pricing guide and the knowledge base and the rest of them, are useful on their own, and you can hook them up to your own systems whenever you have them.
It models the business you already run
Every business has to dictate certain actions under certain conditions. Zorderz lets you set those up, and now we can call it what it is, “conditional logic,” so that any number of steps can be automated and the app knows which tasks belong to which people on your team.
Here is what that looks like in practice. You can designate someone a chief. Then you say that chief is the chief of these particular people, and you can scope it: maybe only for a certain type of service work, or a certain product line, or maybe over that person in general. There are different levels of hierarchy, and each level carries its own rules.
So if you can describe it, you can build it. This employee can do that task during these hours, unless an admin says otherwise. Tell the system once, and it lives on as a rule that gets observed and followed from then on.
Bring your own intelligence
Ai inside Zorderz is bring your own intelligence. Today that means Poe, because a single Poe key reaches nearly every model worth using. Next comes OpenCode, and eventually local LLM harnessing through things like MCP.
On cost, and this is anecdotal: roughly $20 in a Poe account has covered on the order of 10,000 calls to the Ai tools and chats built into Zorderz, and we currently spend about $2 a day, much of which is me testing rather than working. What it would cost you is genuinely hard to predict. Every business is different, and it depends on how many people are using it and how hard they are using it.
Where this field service management software came from
In March 2026, Zorderz started as one private company’s new internal app. It worked well enough that after a while I decided a version any company could use ought to exist, so I started lifting the specifics out. That open version is Zorderz.
Who it is for
I do not know exactly who will use this yet, or why. What I know is that it has been useful in my own business, so I expect it will be useful to others who commit to trying it and judging for themselves whether it is worth it. Anyone comfortable with WordPress can install Zorderz and find out.
And I am learning that an Ai can install a WordPress website start to finish, which changes that sentence quite a bit. If the package is clearly installable and you have an Ai smart enough to reach your web server, this stops being hard. So we plan to ship a document inside the project that explains to an LLM how to install Zorderz for itself, a README at the top of the repository written for an agent as much as for a person. Easy installation is the goal, and an Ai agent is one of the users we are designing for.
After that, the future of the project belongs to whatever community forms around it. I will keep building my version of the perfect field service management software, keep taking the feedback that comes back, and between us we should end up with a better Zorderz than I would have built alone.
What to call it
People describe this category with a dozen different names, so for the record, here are the terms Zorderz is aiming at: field service management software, service business management software, job management software, work order software, small business management software, company management software, client portal software, back office software, a business operating system, open source ERP, a self hosted CRM, and a white label employee app. Different words, same want: one place where the work lives. They are also written down here because I want to remember them, and I would rather keep them on the website than go dig through a spreadsheet every time.
How zorderz.org works
This site is where you can follow the status of the Zorderz platform, and the articles on it get made a specific way. First I dictate the article into a voice memo. That goes to Claude Fable 5, with max thinking and web access turned on, and comes back as a written article. Then I read it and dictate again: what is important, what to keep, what to cut, what to change, what to add, and any statements I want included verbatim and exactly where they go. Those revisions get published as the new version.
The full version history of every one of those passes sits at the bottom of each article, and you can open any of them. The point is to make the thought process legible, including how content gets made now compared to how it used to get made, with a lot of typing and deliberate phrasing and practiced sentences. Now it can be more free association, and then picking out the best parts of what was actually said. I said it once, out loud, and it is what I actually think.
Why it is called Zorderz
The name is about orders. The premise is making orders so easy you could generate them in your sleep, because the platform quietly handles the parts that used to require you to be awake and paying attention.
I am also working out how this should be structured as a business, a public benefit corporation or an LLC, and pricing out what each one would actually cost. There may eventually be something to sell, most likely training on how to configure the platform, though that gets less necessary the moment an Ai can configure it for you. So the monetization question is honestly open right now, and that is fine. The first job is a community, and the rest can develop as we go.
Thanks for coming by, and feel free to contribute to the platform so it gets better for everybody.
— Carleton