Find your next clients without growing your sales team.
We build, inside your company, the system that turns your best delivered projects into your next clients, with the reason to contact them, at the right moment.
See how it worksThree accounts to contact within two weeks, with the reference to present and the message ready, or we keep going at our own cost. The three outcomes →
Missing opportunities, and being beaten to them.
The track record exists, but nothing can be found in it
- Filing archives; it does not retrieve.
- Vocabulary varies from one engineer to the next.
- Nobody searches for what they do not know exists.
- Redoing the work often costs less than finding it.
Accounts that know you sit with no next action
- It is nobody’s job: delivery comes first.
- Calling back without a reason puts the expert in the position of asking.
- Rebuilding the context costs thirty minutes per account.
- The person who knew has left.
The stack costs money and manufactures work
- Subscriptions picked one by one, never designed together.
- The CRM is used as a directory, not as a working tool.
- Nothing is synchronised: data gets retyped from one tool to the next.
- More time goes into cleaning and fixing than into selling.
The first pain is the cause of the second. The legitimate reason to call back exists, it sits in a project delivered four years ago that nobody can find.
One system, delivered in modules.
Your delivered projects
The reference to show
The accounts kept
They see you first
The reason is written
You approve
- You
what comes back as signals
03 engagement · 05 analysed calls · 06 the weekly log
The usual failure is not a shortage of channels, it is that each one aims at its own list: the same account gets approached cold while an account that has followed you for four years is never touched. Here the modules share one list, and what they learn comes back into it.
- 01
The Diagnostic
one to two weeks, with youThe study of your best client cases first, everything follows from it. Then the ICP matrix, the sized addressable market, the scoring grid, the strategy.
- N.
- 02
The signal-based engine
the star of the offerResearch agents review the selected accounts every week, a deliberately small number, not all of tier 1. Prospecting your ICP at the best moment, with the best reason.
- N.
- Apify
- Instantly
- 03
The presence engine
content · ABM adsAlongside the engine, if not before it: the content and the campaigns are aimed at the identified accounts, a prospect who has seen you around no longer arrives cold, and their engagement becomes a signal in its own right.
- 04
The sales memory
depending on the clientYour delivered use cases and studies in a queryable base, a wiki for your sales team.
- N.
- 05
Field intelligence
optional · sales callsFrom first contact to signature, your calls are analysed. Nobody takes notes, what landed and what stalled is captured, and the patterns that keep coming back go to the engine as signals.
- N.
- 06
The follow-up
run with youWeekly or monthly reports, and video calls to go through them.
- You
Seven to fourteen working days. What comes out, and what we need from you.
- 7 to 14 working days
- One-off fee
- 4 to 6 hours on your side
- No tool to learn
Start the signal engine
Watch buying signals and act at the right moment. Walked through by hand once during the Diagnostic, which is what produces the guarantee.
Break down the won projects
The kick-off, then two or three interviews. We isolate what your best projects have in common, and above all what triggered the call at the time: the data written in no CRM, which you only get by asking the person who was there.
The CRM keeps the who and the how much. Never the why now: that one is written nowhere, and it only comes from the person who was there. That is what this step goes after, and why it runs on interviews rather than an export.
Build the ICP matrix
Firmographics, stack, triggers, up to the reference map: which proof to serve which kind of account. A grid, not a hunch.
The fifth level only exists at a company that has delivered projects: an agency has no references to map. That level is what makes the matrix impossible to copy.
Map the addressable market
Count the companies genuinely addressable with that grid. By name, on your territory.
The proportion is an illustration. The real count runs on your grid, and every company kept is named: it is a list, not an estimate.
Score the accounts
A score per account, calculated, never declared. The weights are set with you in a workshop, and complexity weighs most because it is the only criterion specific to your trade.
Starting weights, set with you in a workshop. Complexity weighs the most, the only criterion unique to each client. And the −100 for an excluded sector is a refusal, not a penalty: a grid that cannot say “never” ends up letting everything through.
Collect the signals
On tier 1 only, a person notes what has just happened at each account. No automation, no data subscription: the Diagnostic proves the method yields accounts, not that the tooling holds up at volume.
Collected by hand, on tier 1 only. A signal without a date is a list; dated, it is a reason to call now rather than in six months.
Write the first plays
For each account kept, the five things a play ties together: the dated signal, the reason it gives to call, the comparable project to show, the message written for one named person, and the channel it goes out on.
All four, or the account does not come out. The fourth is what turns “plausible” into “serious”, and it is usually the one that rules an account out.
The read-out
You approve each account in the session, then you decide: build, fix your data first, or do not proceed. All three outcomes are valid, and the third is what makes the other two credible.
The decision is taken that day, not “after some thought”. The third branch is a real exit: it is what makes the other two credible.
Ask your CEO, your account lead and the engineer who delivered. Separately: “what is our best type of client, and why do they call us?” You will get three different answers.
You are not buying the data. You are buying the prepared shot.
- Signal
- A formal notice, dated
- Reason
- A statutory deadline to meet
- Reference
- A compliance project already delivered
- Message
- Written, ready to approve
The engine, shown running: from public signal to a message awaiting your approval.
The Diagnostic is not in this list: it produces the grid the other five run on, and its walkthrough sits higher up this page.
An acoustics and vibration engineering firm, Lyon region. Its track record: seven delivered projects, each documented with what triggered the call at the time. Its market: ten accounts mapped and scored with the firm, seven make tier 1 and go on weekly watch.
The account at the top this week: “Novaline Composants”, a fictional electronic-components manufacturer, 310 people, Grenoble.
The signals detected on this account
A former contact : head of methods at a 2021 client, has taken over as industrial director.
channel: LinkedIn, cross-checked against the firm’s CRM[cross-checked with the CRM, visible to no one else]Announcement of a 30 M€ investment in a new production line.
channel: Trade press, BODACC, press releases[public channel]Job posted: environment and industrial-safety engineer, permanent position.
channel: France Travail, LinkedIn, career pages[public channel]The score, and why this account moves to the front
Each signal weighs according to what it indicates, then decays with age: past its half-life, it is worth half as much. Three different signals stack; the same signal repeated does not count twice.
contribution = weight × 0.5 ^ (age ÷ half-life)
The heaviest signal in the catalogue is also the only one a competitor cannot see: it only exists when the CRM is crossed with public movements. Someone who already knows the delivered work arrives with a fresh budget, and six months to prove their impact.
Below the threshold, an account is not “to be worked this week”. The foundry keeps an excellent fit score, but its only signal, a tender notice. Is 142 days old: the contract has most likely been awarded. The account is still good; it is simply not the one to call now.
The fit score filters the accounts; the signal score orders them. Never the other way round.
The buying committee, identified
| Role | CRM | Concerned by | Source |
|---|---|---|---|
| Industrial director | known to the CRM | S1S2 | Team page on the site, public LinkedIn profile |
| Capital projects manager | not in the CRM | S2 | Public LinkedIn profile |
| HSE engineer | position open | S3 | Published job posting |
Nobody is named: roles stand in for names. Three people, three ways in, and not the same reason to write to each.
The brief: what the engine understood
Electronic-components manufacturer, 310 people in Grenoble. A 30 M€ investment in a new line was announced 41 days ago. An environment and industrial-safety engineer position was opened 19 days ago. Above all: a former contact from the 2021 project, then head of methods, took over as industrial director 26 days ago.
The account stacks three distinct signals, and the strongest is the one that cannot be bought: someone who already knows the delivered work arrives with a fresh budget and six months to prove their impact. The new line raises the exact question of 2021, a vibration threshold imposed by the manufacturer, verified before installation, not after.
Facts on one side, interpretation on the other: when the two blur, nobody knows what has been verified any more.
Why this signal concerns this person
He lived through the 2021 vibration qualification from the inside: the only person on the committee who does not need the problem explained.
The announced investment runs through him; the manufacturer’s threshold is a scheduling constraint before it is a technical one.
The position has just been opened: whoever is hired will inherit the subject with no history, and the first outside contact they meet will count.
The message, with the provenance of every passage
- S1The industrial director’s job change. [LinkedIn, cross-checked with the CRM]
- S2The investment announced for the new line. [trade press, BODACC]
- PThe project delivered in 2021: its sizing note, its compliance measurements. [the firm’s track record]
The third signal, the hiring : is not quoted: it does not concern this person. It opens the conversation with the HSE engineer, not with the industrial director.
The project presented is not picked at random: same constraint, a precision machine whose supplier imposes a contractual vibration threshold, on a site being extended.
The document brought before any reply
For the account under formal notice : fourth in the ranking above, the engine also prepares what gets brought before any reply: a document worked on its precise situation, the only justification for asking for twenty minutes.
Night-time noise-emergence compliance: the six months, step by step
What an accepted compliance file contains, and the two points that cost the most time.
A contradictory emergence survey, a costed reduction study, then acceptance measurements after the works. The order matters: a study without an initial survey is systematically sent back.
built on the project delivered in 2024The six months run from notification, not from publication. On the 2024 case, the initial measurement campaign needed three weeks of favourable weather, a delay nobody anticipates.
built on the project delivered in 2024Treating the source rather than the propagation. On a cogeneration plant, the cost gap between the two approaches runs from one to four.
- It is built on public information and on a comparable case, not on the installation concerned: the actual levels may lead to a different conclusion.
- It does not replace a contradictory survey, the only one that stands legally.
What wasn’t found, and is written as such
- The commissioning schedule of the new line is not public: no way to know whether a window remains before installation.
- No information on the chosen manufacturer, hence none on the applicable threshold.
- No professional email address was found: first contact will have to go through LinkedIn.
An output that finds everything is a fabricated output. What is missing is written down, never quietly filled in.
Illustrative account-to-reference matching output, built on public information. It is not a client result.
- A tender goes outBOAMP, TED, profils acheteurs
- An obligation with a date on itrecueils des actes administratifs des préfectures
- A site gets its permitSitadel, registres numériques d’enquête publique, Géorisques
- A hire that announces a projectFrance Travail, LinkedIn, careers pages
- A company movesBODACC, regional daily press
- PredictLeadsfunding, hiring, new clients
- Trigifywho reacts to your posts, and on what
- Snitcherwhich companies open your site
- ColdIQthe API that aggregates intent sources
Apifyreads the sources with no API
A signal indicates a moment, not an intent to buy. No account is approached without your approval, and the reason is written before the message, never the other way round.
Seven accounts sit in tier 1. The signal engine says which ones are worth the call; this one prepares the ground before that call goes out, on those seven accounts and no others.
The accounts targeted, and what they have already seen
The starting point is not an audience, it is a list. Seven accounts, and for each one what has already crossed their path.
| Account | Exposure | What is missing |
|---|---|---|
| Novaline Composants | The industrial director has followed the firm since 2021 | Nothing recent on the vibration threshold |
| Groupe Alvéna | None | The subject has never been raised publicly |
| Arcolia Mobilités | Two posts seen, no reaction | A format that reads without a meeting |
An account that has never heard of you receives the same message as an account that has followed you for four years. That column is what fixes it.
The subject, drawn from the archive
No editorial line is invented. This week’s subject comes out of a delivered project, chosen because it answers a question three tier 1 accounts are asking right now.
The 2021 vibration qualification: a precision machine, a threshold set by the manufacturer, and a prior measurement that avoided rebuilding a slab.
[the firm’s own archive]When do you verify a contractual vibration threshold: before the machine is installed, or at handover?
[asked by three tier 1 accounts]This is the constraint that makes the module impossible to copy: an agency can write about the subject, it does not have the delivered project that answers the question.
The post, written for those accounts
A vibration threshold set by a machine manufacturer is verified before installation. Afterwards it stops being a measurement and becomes a trade-off.
On a lithography line in 2021, the prior measurement showed the existing slab held the constraint provided a chiller was moved eleven metres. Moving it cost two days. The slab rebuild it avoided cost thirty.
The question to put to the manufacturer before signing: is the threshold expressed in velocity or acceleration, and over which band? The two are not measured in the same place.
The post asks for nothing and sells nothing. It hands over a question to put to a supplier, which is what makes it readable by someone who has never heard of the firm.
The query the ICP actually types
The same material works twice. The project also becomes a page, written in the words the accounts use rather than the trade’s.
| What the trade says | What the client types | What we write |
|---|---|---|
| Vibration qualification | “machine tool vibration limit” | The page, on the wording to the right |
| Regulatory noise emergence | “factory noise neighbour complaint” | The guide, on the wording to the right |
A consulting firm’s vocabulary and its client’s never meet inside a search engine. It is the most expensive gap, and the least visible from inside.
Engagement becomes a signal again
What the post produces does not stay inside LinkedIn: a reaction from a watched account goes back into the signal engine like any other trigger.
The new-works manager at Arcolia Mobilités reacted to the post. He was not in the CRM; he enters it, with the date and the subject that made him react.
[first-party signal: invisible to a competitor]It is the one signal in the catalogue nobody else can see. It cannot be bought or scraped: it exists only because the post went out from you.
What this module does not do
- No community to run, no brand editorial line, no audience advertising. The line that settles it: do we already know who we are talking to? If not, it is brand awareness, and that is not the job.
- No post goes out without approval, no more than any message does.
- No audience is promised and no reach announced: what is shown is what gets prepared, not what the network will do with it.
Illustrative output. The account, the people and the post are fictional; the mechanism and the channels are real. This is not a client result.
Seven delivered projects, their design notes, their measurement reports and the minutes that go with them. Nothing else goes in.
What went in, and nothing more
| What goes in | Volume | Where it comes from |
|---|---|---|
| Delivered projects, broken down | 7 files | The file server, filed by year |
| Measurement reports and design notes | 41 documents | The same server, one level down |
| Meeting minutes | 23 documents | The account managers’ mailboxes |
The original filing archives, it does not retrieve. “Client / Year / Project” does not answer “have we handled a case like this one?”.
The question, asked the way it gets asked
An account manager is preparing a meeting. He is not looking for a file, he is looking for an answer.
“Have we ever handled a vibration threshold set by a machine manufacturer, on a site being extended? And if so, what got stuck?”
Nobody types that into a keyword search, and the vocabulary shifts from one engineer to the next: one writes “manufacturer threshold”, another “supplier vibration spec”.
The answer, and where each claim comes from
The 2021 lithography line and the 2023 foundry extension. The first is closest: precision machine, contractual threshold, existing slab to requalify.
On both files the manufacturer’s threshold was expressed in velocity while on-site measurement is done in acceleration. Converting it took two rounds with the supplier, and three weeks.
The unit of the threshold, the frequency band, and the measurement point written into the contract. All three appear in the 2021 design note, page 4.
An answer without a source cannot be used in a meeting: the client’s first question is “where did you get that?”.
The documents opened
The answer does not replace the files, it leads to them.
Pages 4 and 11: the unit conversion and the measurement point chosen.
[delivered project]Page 2: the gap between the stated threshold and the measured one, and why.
[delivered project]The passage where the manufacturer confirms the frequency band. It is the document nobody can find, and the only one that holds up.
[mailbox, filed into the project]What the base did not find
- No project on a laser cutting machine: the case exists at a tier 1 account, it has no equivalent in the archive.
- What triggered the 2023 project is written nowhere. It can only be obtained by asking the person who was there.
A base that always answers is a base that invents. What is missing is shown, never quietly filled in.
What never goes in
- Nothing from outside: no public database, no third-party content, no other client’s documents. The value of this memory rests on it holding ONLY what the company produced itself.
- Nothing that touches the technical expertise itself. We handle how knowledge circulates, never its content.
- It lives at the client’s, in their name, on their accounts. It does not leave with us.
Illustrative output. The documents, dates and question are fictional; the mechanism is real. This is not a client result.
A first conversation with the industrial director at Novaline Composants, following the message prepared by the signal engine. From first contact to signature, and no further.
What landed, what stalled
Observed inside the call, with the moment it happened. Not guessed afterwards.
The mention of the 2021 project and the chiller moved eleven metres. The other party picks up on his own case without being asked a question.
[the reference, brought in at the right moment]“We already have a consulting firm on our approved list.” The conversation slows for four minutes and only picks up when the subject changes.
[objection, not handled on this call]The question of the threshold’s unit, velocity or acceleration. The other party does not know the answer and offers to check the specification.
[the technical question that repositions]The call captured, and on what terms
| What is set out | How |
|---|---|
| Consent of the other party | Stated when the call opens, refusal carries no consequence |
| Hosting | European Union |
| Retention period | Set in the processing agreement, not by default |
| Scope | Pre-sales only: delivery is never captured |
Capturing a client’s calls makes us a processor of third parties’ personal data. It is the first thing a finance director checks, so it is the first thing written down.
The write-up, awaiting approval
Nobody took notes during the call. The write-up comes afterwards, and it waits for approval before reaching the CRM.
The new line is ordered, the manufacturer is chosen, the vibration threshold is in the specification. Installation is planned for the first quarter, and the slab has not been studied.
A one-page note on the measurement point to impose on the manufacturer, before the internal kick-off meeting.
The kick-off meeting, in three weeks. That date drives the follow-up, not a reminder in a calendar.
The cross-reading, across all the calls
One call says little. The report only goes out once there is enough to cross-read, and it says what keeps coming back.
| What comes back | Where it happens | What we do with it |
|---|---|---|
| “We already have a firm on our approved list” | The first third of the calls | A prepared answer, and a test: approved for which kind of project? |
| The question of the threshold’s unit | After a reference has been presented | It moves to an opening question: it qualifies faster than it convinces |
| Mentioning a comparable project | At the point where the conversation slows | It moves earlier in the outline |
The report goes out at a regular interval, and nobody writes it. That is why it still exists three months in.
What goes back into the engine
This is the only feedback loop in the offer. The signal catalogue is derived once, during the Diagnostic; here it gets corrected on live deals.
“Machine manufacturer selected” becomes a watch criterion: it comes months before the works tender, and it is sometimes public.
[a pattern heard becomes a signal watched]The question of the threshold’s unit becomes the subject of a post: it is the market’s wording, heard three times, not the trade’s.
[real words feed the content]What this module never does
- It does not score salespeople. It analyses deals, never people. The moment a call analysis tool is used to rate individuals, nobody speaks freely in front of it and the corpus turns false.
- It covers pre-sales only, from first contact to signature. After that it is delivery, and we do not go there.
- Nobody from NateSystem picks up the phone: the conversation belongs to the client.
- It does not index technical content. What triggered and what landed, never the solution: the technical expertise stays out of scope.
Illustrative output. The call, the other party and the timestamps are fictional; the mechanism and the legal terms are real. This is not a client result.
Three hours fifteen a week on the run side, two of them spent matching accounts to the archive on Monday morning. This report is what comes out of it.
The week’s log
| What ran | This week |
|---|---|
| Accounts watched | 7, all tier 1 |
| Accounts that crossed the threshold | 3 |
| Plays prepared and submitted | 3 |
| Plays you approved | 2 |
| Plays turned down | 1 |
No reply, meeting or revenue figure appears here, and step 05 says why.
What was turned down, and why
This is the most useful line in the report. One refusal says something about the grid that ten approvals do not.
The signal was right, the reference was not: the comparable project offered covered a site being extended, this one is new build. The constraints have nothing in common.
[turned down on the reference, not the account]The account is not dropped: it goes back into preparation with another project from the archive. The matching failed, not the selection.
What changes in the grid
Calibration is not an internal setting: every change is proposed, argued and approved by you before it applies.
| What we propose | Why | Status |
|---|---|---|
| Split extension and new build in the reference map | Refusal R1: the two are not handled the same way | Awaiting approval |
| Add “machine manufacturer selected” to the signal catalogue | Heard three times in meetings this month | Awaiting approval |
| Lower the weight of HSE hiring from 4 to 3 | Too many accounts trigger it with nothing behind | Applied 21 August |
The weekly session
Thirty minutes on video, with the agenda written beforehand.
- The three accounts that crossed the threshold, and the order to take them in.
- Refusal R1, and which project to match it with instead.
- The two grid changes waiting for your approval.
- What the archive lacks: no project on a laser cutting machine, while a tier 1 account runs one.
What is not measured, and should be
This report says what the machine produced. It does not say what the market did with it, and nothing in the offer measures that today.
- What went out, and what got a reply: the loop is not closed. No result figure will be put forward before a first client is measured, before and after.
- The real time spent preparing an account, before and after the system is in place. That is the measurement missing most, because it is the one that would make the value demonstrable.
- What needs to come out of it is written down; who writes it, where, and how often, is not.
While that measurement is missing, every engagement produces value without producing proof. It is the first open build in the offer, and it is written here rather than left unsaid.
Illustrative output. The accounts, counts and trade-offs are fictional; the weekly workload and the mechanism are real. This is not a client result.
Five ways to go about it. What each one leaves behind.
| NateSystem | Hiring a salesperson | A prospecting tool | An agency | Building in-house | |
|---|---|---|---|---|---|
| Time to the first deliverable | 2 weeks | 6 to 12 months | immediate, untargeted | 1 to 2 months | 6 months or more |
| Share of your track record used | all of it | none | none | none | varies |
| What remains at the end | the system, the code, the grid | nothing if the person leaves | a subscription | nothing | the system |
| Who approves before anything goes out | you | — | no one | the agency | you |
What we get asked before we start.
An agency is judged on activity figures : opportunities opened, appointments booked, response rates. Numbers that no measured case allows us to promise, so we promise none. Three things cannot be copied: the accounts come from your delivered projects, not from a purchased list; you own the system and its code; and nothing goes out without human approval, account by account.
Because it is written here rather than discovered in a first call. What exists can be verified: an engine running on public data, 80% noise measured on a real sweep, and the exact shape of the deliverable shown above.
The first client will be measured, before and after, and no result figure will be put forward until then.
It happens, and it is a planned outcome of the Diagnostic: fewer than ten usable projects, or none whose trigger can be reconstructed, and the conclusion is “do not proceed”. We tell you so and we stop there.
The Diagnostic is a fixed two-week engagement; the amount is given out loud, in the first conversation. What follows is custom, quoted as a number of build days, never a catalogue of features.
What de-risks the commitment is written on this page: three accounts in two weeks or we keep going at our own cost, and a Diagnostic that can conclude not to proceed.
Your team does. The system prepares the account, the reason and the message; nothing goes out without human approval, account by account, never in bulk. The conversation that opens belongs to you: we do not take over the closing.
No. Your CRM stays the source of truth: after approval the engine writes a task and a note into it, plus two prefixed fields. Nothing else.
The line that settles it: do we already know who we are talking to? If yes, it is content aimed at identified accounts. That gets done: it is the presence engine. If not, it is brand awareness: an entire trade of its own, judged on indicators that no measured case allows us to promise, and it is not ours.
The system. It is neither software you rent nor an agency you pay by the month: what gets built is built inside your company, in your own software accounts, in your name. And whatever the system lacks is displayed, never quietly papered over.
Never. Acoustics, thermal engineering, structural calculation: your domain. We handle how that knowledge circulates and gets reused, not its content.
Is your next priority already sitting in your own data?
A first 30-minute call to understand your situation, your sources and which level of engagement fits. If this is not for you, we will say so during the call.
or email directly at nathan@natesystem.com- Free, with nothing to prepare
- You leave with a read on your situation, even if it goes no further
- If the timing is wrong, we say so
My story.
I built business software for small and mid-sized companies, across very different setups. The same thing came back every time: the tool was never the problem.
What turned NateSystem towards acquisition fits in one sentence, said by a project manager at an engineering firm: you do not get into a company by offering to add another internal tool, you get in by bringing clients.
I take your call, scope the work, deliver it and train your team: from the first conversation to production. We take on few projects at a time, and that is stated at scoping rather than discovered when the schedule slips.
What happens if I am no longer around? The answer is not a promise. It is written into the contract and into the technical choices: the code, the accounts and the data are in your name.
Real screenshots, blurred at the clients’ request. None of them is a mock-up.
The machine handles the volume: retrieving, connecting, dating, matching, preparing. The decision stays with a person, every time, and nothing goes out without their approval.
professional data onlysource and reason documentedone-click permanent unsubscribeEU-hosted wherever possibleyou own your data and accountsFull practice →