Twenty years of engineering behind the code, and a shop of our own that taught us what the software was costing us. One subscription with everything in it — no cut of your money, and the person who answers your email wrote it.
AI-first, and agentic — every plugin ships with two agents: one facing your customer, one facing you.
You know the pattern. The plugin does eighty per cent, and the last twenty is four add-ons at $49 each. Twelve plugins from twelve vendors, so the Tuesday one of them updates is the Tuesday checkout breaks. And the day a licence lapses, a plugin that switches itself off and takes your shop with it. We are building the plugin company that refuses all of it — in public, before we have sold anything.
Refusing things is only half of a company. We have run a business that lives on its diary, so we build for the week you actually have — priced monthly so you can start long before you can afford a year, and set up with you, on a call. We stay on the line until it is running.
Nothing has been sold yet. Every number here is countable in the repository, and the things that are not built say so.
And more after that. We build fewer plugins, deeper.
The name
Sellers, buyers, and a set of rules everybody trusts enough to turn up for. It works when both sides leave happy — the seller who got paid on time, and the customer who got exactly what they came for. Everything a market needs is what a business needs: know who is coming, hold the goods, take the money cleanly, and be there when something goes wrong.
Sokocode is the code that runs that market for you. Not a plugin that stores a booking — the rules, the money and the follow-up, so both sides of your counter walk away wanting to come back.
Money taken cleanly and confirmed before anything is marked done, invoices that survive an audit, and not a rupee of it skimmed by us. Whatever you sell, the gap between a customer deciding and the money actually arriving is where most of it goes missing.
No account to create before they can do the thing they came to do. No dark pattern hiding the way out. A page that works on the phone they actually own, and the freedom to change their mind at eleven at night without having to speak to anybody.
Guarantees the database enforces, not conditions the code remembers to re-check. Careful code buys you “usually” — and a market where the rules only usually hold is a market people quietly stop coming to.
More than software
Most plugin companies have never run the business they sell to. We did — badly, at first, with a diary full of holes and a number we could name to the rupee every month. That is a different starting point from a feature list, and it shows up in what the software does when you are not looking at it.
The customer who did not turn up. Two people sold the same thing. The three evenings lost to setup. The payment that cleared while the order never did. We build for the gaps between the features, because that is where the money actually goes — not for a comparison table.
It notices things. It chases the ones worth chasing and closes the loop on its own. It tells you each morning what needs a decision and what is already handled — before the day starts, and without being asked.
Every screen hides what your data says you do not need, so nothing arrives switched on and half-set. Competing plugins are cluttered because nobody ever said no to a feature. Saying no is most of the design work.
Fifteen minutes from install to live, because sensible defaults arrive already filled in and tax arrives configured for your country. The parts that stop the software being wrong are on before you touch a single setting.
A migration is a call, not a support ticket: we sit on the dry run and read the report with you. No charge, and no sales pitch at the end of it. The fastest way to learn what a business needs is to watch somebody set one up.
WordPress core moves, PHP versions retire, and payment providers rewrite their APIs without asking you. That unglamorous work is most of what a licence actually pays for, and it is the part a company has to still be around to do.
Why we are different
None of these is a bug. They are all business models — decisions somebody made on purpose, which is why complaining about them never changes anything and building differently does.
| What usually happens | What we do instead |
|---|---|
| The plugin does eighty per cent. The last twenty is four add-ons at $49 each. | One subscription, everything in it. There is no module to buy for payments, coupons, custom fields or reminders. |
| Twelve plugins from twelve vendors, so the Tuesday one of them updates is the Tuesday checkout breaks. | Fewer, deeper plugins from one team that tests them against each other before you do. |
| “Please deactivate all other plugins and try again.” | The engineer who wrote the code reads your message, 24×7, with the source open. There is no tier one. |
| Renewal was half price the first year. It is not any more. | No permanent fake discount. When we discount, the offer carries a real end date, and the price you saw is the price. |
| The licence lapses and the plugin switches itself off, taking your shop with it. | Expiry never breaks your site. Bookings, payments and reminders carry on. You lose updates and support, not your business. |
| Every plugin loads its own CSS and JavaScript on every page, whether the page uses it or not. | No framework, no build step, nothing fetched at runtime. The wizard brings one stylesheet and loads where it is used. |
| The plugin gets sold to a portfolio company, and the updates stop. | Fifty-five dated releases, and a page listing what is not built. You can see the pace before you buy. |
| Forty settings to configure before anything works. | Defaults over settings. A feature is implied by your data, never by a toggle — a one-person business is never asked to pick a practitioner. |
| They take a cut of every transaction, on top of the gateway's. | Zero fees, forever. Money moves between your gateway and your bank without passing through us. There is nowhere for it to pass through. |
What you are actually buying
Support, AI, performance, price, design and security are on every software page ever written, which is exactly why they have stopped meaning anything. Each one below says what it is, specifically enough that you could hold us to it.
What we build
Multi-practitioner scheduling, thirteen payment gateways, GST invoicing, two-way WhatsApp, deposits, packages, events, clinical notes, outcome tracking, an AI agent on the booking form and a copilot in the admin. Sixty-four capabilities, thirty-three industries, and a free plan that takes real money.
Discount rules a shop owner can build without a developer — tiered pricing, buy-one-get-one, cart conditions, first-order offers and referral attribution. Every scheduled offer takes an end date, because a company that refuses permanent fake discounts should probably ship the tool that makes them expire.
Recurring billing for WooCommerce, including the parts Indian sellers actually hit — RBI e-mandate rules, pre-debit notice, tokenised cards, and dunning that assumes a renewal will fail sometimes. The equivalent extension elsewhere is $199 a year.
Neither has been started, and neither has a date. They are named here because a plan you can hold us to is worth more than a wall of tiles saying coming soon. When one exists it appears here with a version number and a changelog, the same as the first.
The covenant
These are not features, they are refusals — and they apply to everything we build, whatever it does. When the products have nothing in common, this is what does.
A promise made after the money has changed hands is a marketing message. Made before, it is a constraint.
One subscription with everything in it. There is no module to buy for payments, none for reminders, none for the feature you assumed was included. One invoice a year.
We sell a licence, not a percentage. Money moves between your gateway and your bank without passing through us — which is also why we could not take a cut if we wanted to.
Whatever stops the software being wrong is free in every plan, including the free one. A cheaper tier that can corrupt your data is not cheaper. It is broken.
Everything is self-hosted, on your WordPress, on your server. No telemetry, no analytics beacon, no remote script at runtime. Our plugins do not phone home.
Not on the first reply — an autoresponder meets a first-reply target. Same day on anything critical, on every paid plan, from the engineer who wrote the code.
No questions, no exit interview, no form with a dropdown of reasons. Longer than anyone we compete with, because a month of real use is what it takes to know.
When a licence lapses the plugin carries on exactly as before. You lose updates and support, not your business. We will never ship an update that holds your site hostage.
Every plugin shop in this market runs “normally $499” with no end date. When we discount, the offer has a date on it and the date is real.
AI-first, structurally
Everyone shipped an AI button this year. Almost nobody published what theirs is not allowed to do. We build every plugin agent-first — the REST route comes before the screen, so anything a person can do, an agent can do too — and the rules below apply to all of it.
It answers in plain language and then does the thing — fills the form, finds the slot, applies the code. Presented as a search box rather than a chat bubble, because a bubble is trained as support and invites exactly the questions it must refuse.
Never invents a priceAsk for it in a sentence and it plans, checks with you, then acts — the bulk reschedule, the price change, the export. Every write audited with who asked and what they said, and every one of them reversible.
Never acts unapprovedEvery time and money figure in a reply is extracted and checked against what a tool actually returned. The guardrail is in the code, not in the prompt — a prompt guardrail fails silently the day somebody swaps the model.
Capability is checked per tool, against the operator. An agent can never do something its user could not have done by hand, which makes the blast radius the same as the login.
Nothing irreversible happens without a human approving the plan first. Ambiguous names return a list rather than a guess, and bulk operations are capped.
Each operation is remembered so it can be reversed, and every write records who asked and what they said. An agent you cannot undo is a liability with a chat window.
Switched off, an agent renders nothing at all — never an error, never a greyed-out box with an upgrade prompt. The product works without it, or it is not a product.
Bring your own provider. Nothing reaches a model unless you turn it on, and none of it passes through us — there is nowhere for it to pass through.
Your bookings, your customers and your notes are never used to train anything — not by us, because we never receive them, and not by the provider you chose, because that is a setting you control on your own account.
When it is not sure it says so and passes you to a person. An agent that would rather be wrong than silent is the one that costs you a customer, and confidence is the cheapest thing a model produces.
The question worth asking is not what the AI can do. It is what happens when it is confidently wrong at 8pm on a Friday.
The agent in the corner is ours, running every rule above. It answers from the documentation, routes you to the right page, and hands you to an engineer the moment it is not sure rather than inventing something plausible.
A booking assistant that fills the form for your customer, and an admin copilot that plans, asks, then acts for you. Plus a third that uses no model at all, which is the one that speaks first.
No customer count, no star rating, no trusted by 100,000 businesses — because nobody has bought anything yet, and a badge you cannot back is the cheapest thing on any software page.
Why we exist
Not a market study. Not a gap in a category matrix. We paid for software to run a working practice, it lost money every morning, and when it broke the answer was a ticket queue and four days of silence. Every refusal above is that experience turned into a rule.
How we build
When the products have nothing in common, the method is the quality guarantee.
Every feature earns its place in the screen your customer sees and the screen you work in. Competing plugins are cluttered because nobody ever said no. We say no.
The practitioner step disappears below two practitioners. The coupon box appears when a live coupon exists. If the software can work it out from your data, it should not be asking you.
The best version of a change removes a branch rather than adding one. The smartest solution is almost always the shortest correct one, not the most general one.
Constraints the database enforces under its own locking, not conditions PHP re-checks afterwards. A unique index makes a thing impossible; careful code only makes it unlikely.
Parameterised SQL, a nonce and a capability check on every action, output escaped at the point of use, and money recomputed on the server every single time.
No interface with one caller. Two similar things are a coincidence; three are a pattern. Building the abstraction early is how a codebase becomes elaborate before it becomes useful.
A guard that fails loudly beats defensive code that hides the problem. The importer refuses by name when a column is missing rather than importing nothing and calling it success.
Two settings that mean the same thing will disagree eventually, and the person who has to work out which one won is you, at the worst possible moment.
Roadmap items are labelled as roadmap, and there is a page on this site listing what has never run in production. We would rather tell you than let you find out on a Tuesday.
Some features sell well and should not exist. No symptom triage, no dark patterns in a cancellation flow, no add-on shelf. Saying no to those is most of what makes the rest trustworthy.
One account
Everything we ever release lands in one account, on one licence, at one price. Buy a second plugin and it lands in the account you already have — same invoice, same renewal date if you want it, same engineer answering. No second shop, no second password, no second support address.
Leave an address and you get one email when the first plugin ships and one when the pricing is final. Not a newsletter, and never a drip sequence.
Two emails, then nothing. We do not sell lists.
Start somewhere
Appointments end to end, on your own WordPress, free for one practitioner with no card and no clock. Every promise on this page applies to it.
Design reference. This one answers from a fixed list, with no model behind it. The real agent will call our own endpoint — never OpenAI directly, because a key in this page is a key anyone can read.