About
Built for businesses that sell through conversations
Most revenue tooling assumes a form fill and a CRM record. A lot of the world sells over WhatsApp, and none of it fits that shape.
The problem we started from
A freight forwarder gets a rate request on WhatsApp at 9pm. A property consultant gets a brief over email and a follow-up on a phone number nobody has recorded. The enquiry is real, the intent is high, and it lands in a shared inbox that four people half-watch.
The tooling that exists either assumes web forms and a marketing automation funnel, or it is a shared-inbox product with no idea what a pipeline is. So businesses run on a spreadsheet of follow-ups, a CRM nobody updates, and an ad account whose numbers cannot be connected to anything that closed.
What we decided to build instead
One customer graph underneath everything. A contact is a person, not an email address — they can be reachable on several, and messages from any of them join the same timeline. Every touch is recorded, so attribution is a question you can answer rather than a model you assume.
On top of that: an inbox that treats WhatsApp's constraints as real rather than as an inconvenience, AI agents that are governed by rules enforced in code rather than requested in a prompt, and a sales layer whose stages and qualification fields are configuration.
“Most revenue tooling starts from a form fill. Ours starts from a conversation.”
How it is built
By one person, full-stack, which shapes almost every technical decision you can see. Six screens are hand-built because they are the product; the rest are generated from the same schema definitions the backend uses. There is no unit-test suite — tests drive real code against a real database, because a test asserting a gate returns “block” in isolation proves nothing about whether every send path calls it.
Several choices look wrong without their reasoning, and we would rather publish the reasoning: ad platforms are read-only, identity merges are deterministic only, there is no public REST API in the first release, and workflows are configuration rows rather than a visual canvas. Each of those is a trade, made deliberately, with a condition that would change it.
Where we are focused first
Freight forwarding and 3PL, then commercial property. Both qualify on a handful of structured facts, both genuinely use WhatsApp and email, and in both a slow response loses the deal. Nothing in the product is specific to either — see logistics and property.
The company
Linkubit is operated by {{LEGAL_ENTITY_NAME}}, registered at {{REGISTERED_ADDRESS}}. Founded {{FOUNDED_YEAR}}.