Every tool you run produces a feed. On its own, a feed means nothing.

Your website produces a feed of visits. Your helpdesk produces a feed of tickets. Your email tool produces a feed of opens and silences. Your product produces a feed of payments and failures. Four feeds, running all day, every day, and each one is just a list of things happening to nobody in particular. Feedbank is the bank those feeds run into. It holds them together, works out which entries belong to the same person, and turns the combined feed into something with meaning — one sentence, when something is worth knowing. It replaces nothing. The feeds keep coming from where they already come from. Feedbank is what happens to them next.

/ THE IDEA IN THREE PARTS

The feeds arrive. They are matched. They mean something.

1. The feeds arrive

Every tool you connect starts pouring its feed in — a page visited, a ticket opened, an email ignored, a payment that failed. Nothing is asked of you, and the tool carries on exactly as before.

2. The feeds are matched

The same person appears in four feeds under four different names — an email address here, an account number there, an anonymous visitor somewhere else. Feedbank works out which entries are the same human and banks them against one record.

3. The feed means something

A combined feed can be read in a way four separate ones cannot. Rules read it and write a plain sentence when something matters. You choose which of those are worth an email and which wait until you look.

/ INSIDE THE BANK

What the bank is made of.

Sentences the system writes

Seventeen rules read the combined feed and write what they notice — someone who has gone quiet, a page most readers abandon, people who tried to contact you and could not. Each finding carries the evidence behind it, so you can check it rather than trust it.

Every part is included. There is no higher tier that unlocks the useful half.

See it working

What actually happens, from a click to an email.

A line lands in the feed

Somebody visits a page, sends a message, cancels, or fails to pay. Whichever tool saw it pushes that one line into Feedbank, within seconds.

It is banked against a person

Feedbank looks for someone it already knows with the same email or account number. If it finds them, that line joins their feed. If not, a new record opens. If the feed offers nothing to match on, the line stays with the feed rather than being guessed onto the wrong human.

The combined feed is read

Every five minutes the rules read across every feed at once. Most of the time they find nothing worth saying, which is the normal and correct outcome. When one does match, it writes a sentence and attaches the evidence.

You are told, or you are not

If the finding matches something you asked to hear about, it is emailed. Otherwise it waits in the app until you open it. Nothing is invented to fill a quiet week — you are told the week was quiet and why.

The customer who slipped away

USED TO BE: a good customer stops buying. You notice three months later while looking at something else, and by then they have gone somewhere else. NOW: “Sarah Jenkins has not been seen for 34 days. She was worth £900 last year and she opened a support ticket the week before she stopped.” You ring her while it still means something.

The enquiries that never arrived

USED TO BE: your form gets three enquiries a month and you assume that is simply the demand. NOW: “Eleven people started your quote form this week. Three finished it. Seven of them stopped at the postcode field.” The demand was there. The form was eating it.

The people who tried to reach you

USED TO BE: nobody rings, and there is no way to know whether that is because nobody wanted to. NOW: “Four people reached your contact page this week and none of them got in touch.” It turns out the phone number is not tappable on a phone. That is a ten minute fix worth four enquiries a week.

The quiet buyer

USED TO BE: an enquiry arrives out of nowhere and you treat it like any other cold lead. NOW: “This person read your prices four times over nine days and came back from a WhatsApp link before they wrote to you.” You already know they are serious, and what they were worried about.

The complaint you did not connect

USED TO BE: a support ticket is answered and closed, and nobody links it to the renewal that quietly does not happen six weeks later. NOW: “This customer opened a ticket, has not opened an email since, and their renewal is in three weeks.” One conversation instead of one lost account.

/ WHAT CHANGES

Five things that are different once it is running.

Not features. What changes once the feeds are read together.

You find out in days, not months

The gap between a customer going quiet and you noticing is where most losses live. It shrinks from a quarter to about a week.

You stop opening four tabs to answer one question

Everything about a person is on one screen, so “what is going on with this customer” takes ten seconds instead of a morning.

You fix things you did not know were broken

Forms that lose people, pages nobody finishes, a contact number that does not work on a phone. All invisible until something counts them.

You walk into calls already knowing

You know what they read, what they asked, and what they ignored before they ever say a word.

Nobody has to remember to look

Being told is different from being able to find out. A report you have to open is a report you eventually stop opening.

WHAT CHANGES

Questions people ask while they are working out what this is

See it working

Why is it called Feedbank?

Because that is literally what it is: a bank for your feeds. Every tool you run produces one, they all run separately and mean very little on their own, and this is where they are held together and turned into something you can act on.

Is this a CRM?

No. A CRM is where your team writes down what it did — calls made, deals moved, notes typed. Feedbank is where your tools write down what the customer did, without anybody typing anything. There is no pipeline and nothing to keep up to date. Most people run both.

Is this just website analytics?

Analytics reads one feed — the website — and reports on a crowd: visits, bounce rate, time on page. Feedbank reads every feed you have, including ones with no website in them at all: payments, support, email. The website is one feed of several, and the meaning comes from combining them.

Do I have to change how I work?

No. Every tool you use today keeps working the same way, and nobody on your team does anything differently. Feedbank reads what already happens. If you switched it off tomorrow, nothing in your business would stop.

How does it know two records are the same person?

By email address, by the account number your own system already uses, or by an anonymous visitor who later signs in and gives themselves a name. Where a source offers none of those, the information stays with the source rather than being attached to a guess — a wrong match is worse than no match.

What if there is nothing worth telling me?

Then it says so, and says what it is waiting for — nobody has identified themselves yet, there is no form to abandon, there is not enough traffic yet to be sure of a pattern. Filling a quiet week with something invented would make every other week worthless.