What people come with most often
Five pieces of work in this section. The first two are about who signs in; the other three are about what the portal lives on.
A portal for your customers
A task in plain words, files, an estimate before the start, the status of the work and sign-off on the result. Customers stop calling to find out what is going on.
Read more →A portal for partners and dealers
Enquiries with a source tag, customer records, the share calculation and analytics. "Whose customer is this?" is settled by a record, not by memory.
Read more →A portal with an assistant
The assistant answers from your own materials and helps the customer describe the task. A label next to the answer says a machine is speaking.
Read more →Linked to the website, CRM and accounting
A website enquiry arrives in the portal with its source tag, the status from your system is visible to the customer, and documents are not typed in twice.
Read more →An internal portal for staff
An honest look: when a portal for your own people is worth building to order, and when an off-the-shelf one is cheaper. We say it out loud.
Read more →A portal is not a CRM. A CRM looks inward at your company; a portal looks outward, and your customer or partner works inside it. The two do not compete and usually stand side by side.
When people come to us with this
Four situations where a portal pays off first.
"So what is happening with my order?"
That question arrives every day and through every channel at once. You already have the answer — it just sits somewhere the customer cannot reach.
The status lives in a manager’s head
They go on holiday and nobody can say which step the work is on. The only written record is a chat thread, and different people read it differently.
Dealers and partners order by email
The request arrives as a message, someone copies it into a spreadsheet, and once a month the share calculation becomes a job of its own.
Documents are hunted for in the chat
The invoice, the contract, the act and the latest version of a file live in four different places and get resent every time.
What stays with you afterwards
One place where the state of things is visible
Your customer or partner signs in and sees their tasks, the status, the files and the documents. Around the clock, and the same for both sides.
Questions stop being work for people
A person answers where a person is needed, instead of retelling what is already written down. A message that arrives at night gets an answer straight away.
A written history instead of an argument
Who asked for what, when it was agreed, what was accepted — a record, not anybody’s memory. A source tag cannot be added after the fact, so the calculation stops being a matter of faith.
A clear order, no surprises
1 · A conversation
Half an hour about who asks you what, and how often: customers, dealers, partners, staff. No access to your systems is needed at this step.
2 · A map of the questions, and the first screen
We show which questions eat your people’s time and pick what the portal closes first — usually the status of the work and a place to put files. The map stays with you either way.
3 · We take it into service
We build the portal, connect it to your systems, open it to the first users and stay around: we watch what they actually use and tell you what changed and why.
The figure is named in a quote for your task, once it is clear who signs in, what they do there and which of your systems the portal talks to. There is no price list here on purpose: the spread of work is very wide, and an "average price" would mean averaged work.
Look at the work, not at the words
The first two figures come from the records of our own platform — the very one this section is about; the third is about the agency as a whole rather than about portals. The caption and the period under each number are set by code at build time, not typed in by the author.
preparing data…
Every figure is exported from the agency logs by code at build time, not typed in by hand. Periods: 61 — 4–9 August 2026; 24 — 4–9 August 2026.
Where the figures come from
- business lines running at the same time
How many different businesses the agency runs at once. A line counts if it has at least three tasks in the log; internal test runs do not count.
What we do ourselves and what we do with partners
We do this ourselves
The customer portal and the partner portal are our own product, not somebody else’s system we rent. We run it ourselves: partners sign in every day, and the customer portal lives on this very site. We can show you a working one immediately, not a mock-up.
Outward-facing portals — for customers, dealers, partners — we build end to end ourselves: sign-in, tasks, statuses, files, documents, invoices, notifications and the assistant inside.
We build this out for you
The link to your accounting system depends on what you already run. What connects straight away, what goes through an export and what does not connect at all — we say in the review, before the work starts.
We run this with a partner
An internal portal for staff we look at separately and honestly: there the task is often solved more cheaply by something off the shelf, and we are not going to sell you bespoke work to keep the order round.
Where a partner does part of the work — say, your accounting system is extended by its own contractor — we stay your single point of contact: we set the task, watch the timing and answer to you for the result. The contract names the contractor honestly — no "we do everything in-house".
What people usually ask
How is a portal different from a CRM?
We already have a CRM — will we have to replace it?
Can we see a working portal rather than pictures?
Let us look at your task
Half an hour about who asks you what and how often — no access to your systems and no commitments.
We call back during working hours. Company details are optional — if you give them, we read the open registries first and come to the conversation prepared.