Marketing
The tools each hold a fragment. None of them holds the picture.
The audit tool knows the site is slow. The content tool does not, so it keeps writing posts that land on a page nobody stays on. The customer system knows a lead went quiet in week three; the scheduler does not.
Where the decision happens
- Records you already keepSpread across the systems you already run.
- One finding, with its evidenceDrawn together into a single proposed action.
- A person approves itThe drafted action waits; approving is what sends it, under their name.
- The work goes outAnd the reason stays on the record.
Where it goes wrong
-
Every step waits for the one before it
Brief, draft, review, schedule. Turnaround runs in weeks and the market moves in days — which decides whether you can answer a competitor's announcement at all.
-
Generic in, generic out
A writer without your customer records, your positioning history or your pipeline works from your website and their own sense of the sector. That produces competent, forgettable copy.
-
The effort does not compound
Every campaign starts from a blank page, because nothing learned in the last one was written down where the next one could read it.
-
The brief is the exposure
To write well about you, whatever is writing needs your pricing logic, the competitor you actually lose to, the names in your pipeline. The better the brief, the more sensitive material sits inside it.
Who owns this
A team of one to five marketers with more to say than hands to say it. These are the people Runink PULSE is built to change the week of.
-
The marketing lead
Your time moves from producing material to deciding about it. PULSE's approval queue becomes the surface you work on.
-
IT and information security
The reasoning and the writing run on your servers, your cloud or ours, never at an outside AI service. That is a property of the Runink TIDE platform PULSE runs on, not a setting somebody in the marketing team has to remember to honour.
-
Sales
PULSE researches a prospect and drafts a cold email, a call script and a direct message per company, and leads synchronise to the customer-record system the team already works in.
-
The board
PULSE's multichannel analysis comes out as a written document you can put in front of people, not a dashboard somebody has to narrate.
What Runink PULSE changes
- One PULSE diagnosis feeds the channel analysis, the content plan, the schedule and every draft, so what goes out carries one argument rather than four versions of it.
- Every draft — post, whitepaper, cold email, call script — lands in a review queue with an approve and a reject, and approving is a step a named person takes rather than a formality the system performs for them. Read it as the place the work is cleared, not as an interlock wired across every route something could leave by.
- Every piece has one stated status: draft, waiting for review, approved, rejected, published, archived. Those six are the statuses PULSE actually keeps, so what is waiting on you and what actually went out are both visible.
- Marking a PULSE result useful or not carries into the next round, so understanding accumulates in a system instead of in one person's head.
How you will know it worked
These numbers are yours, not ours. Write down where you stand in the first week — once the working rhythm changes, the thing that would tell you where you started is the thing that changed.
| The measure | Your figure today | What moves it |
|---|---|---|
| Cost per published piece | Last twelve months: agency retainer and project fees, the salary cost of hours spent briefing, reviewing and chasing, and per-seat tool costs. Divide by the pieces actually published, not the pieces commissioned. | Down on both halves of the fraction — producing a draft stops being the expensive step, and fewer commissioned pieces die before they reach a page. |
| Commissioned but never published | The same twelve months, from your brief log or project tool: briefs that died in revision, pieces abandoned when the moment passed. Cost with no output against it. | Down, because a draft exists the same day the brief does, and each one then sits in a queue with a stated status instead of going quiet. |
| Median days from decision to publication | Take five recent pieces: the date somebody decided to say the thing, and the date it went out. Use the median, not the average. | Down, because the elapsed time becomes the time a person needs to read and approve rather than the time a piece needs to be produced. |
| Coverage against the questions buyers actually ask | The channels and formats you agreed are worth being present in, with pieces published against each last year — plus the questions sales gets asked that no page on your site answers. | The near-empty rows fill. Those rows were a decision your production capacity made on your behalf; the mechanism is that the decision comes back to you. |
| Qualified pipeline sourced, and time to qualify an inbound lead | Your customer-record system, over a quarter: the gap between a lead arriving and the stage change marking it qualified or disqualified, and the share of sales hours spent on leads that never qualified. | Time to qualify down, qualified share up, because PULSE attaches research on that specific company to the outreach instead of leaving it to be assembled by hand afterwards. |
| Organic visibility, and how the site reads to search engines | Impressions and clicks from your search console for the trailing quarter, alongside a scored audit of the site kept from your first day, before anything is changed. | Up, because PULSE's audit returns its recommendations ranked and applies them from the same screen rather than exporting them to a ticket somebody opens in a fortnight. |
Two things that make the above possible — and neither is a marketing feature
-
No outside AI service learns from your material
The analysis and the writing happen on the machines PULSE runs on. Customer lists, pricing logic, unpublished plans and positioning you have not announced are processed there, not handed to an outside model provider to learn from. This comes from the Runink TIDE platform that PULSE is deployed on — the layer that runs the software and holds the connections to your own data — rather than from anything in the marketing product itself.
- What you would notice
- The review that stands between a marketing team and a new tool. When legal or security asks where company material is processed, the answer is the name of a machine, given once and in writing — the same answer a customer's security questionnaire and a data-residency clause need.
-
Open-web research that does not announce itself
PULSE reads the public web directly, through Runink's own headless-browser engine driven over ordinary public search results and the pages behind them, rather than putting your questions through a search company's paid service. The engine is shared Runink infrastructure, not a PULSE feature — PULSE is one of the products that uses it.
- What you would notice
- Competitor and pricing research is where the question gives away the plan: asking a vendor about a rival's pricing tells that vendor you are working on pricing, and that record sits outside your control. It also means how much research a campaign gets is decided by the campaign, not by a per-question bill or a monthly cap.
Who you would be working with
Runink is founder-led. The person in the first meeting is the person who designed the thing being discussed — his track record, what he does here, and the means to check any of it are on the company page.
See whether it fits
Bring your website and the channels you publish on. Reading them and telling you where you stand is the first thing PULSE does, which is also the fastest way to judge whether the rest is for you.
Runink PULSE is the product behind this page, and it is a different product from Runink FACE — nothing described above is a FACE capability, and nothing on the FACE pages is a PULSE one. The paper carries no case studies, no customer names and no return-on-investment figures.