Marketing automation for marketing teams and SMEs

We help overworked marketing teams and SMEs automate half or more of their marketing tasks, so the work gets done without adding people.

All marketing teams have one thing in common: the same tasks come back every week and take hours each time.

We've been part of those teams, in marketing and in operations, and we know which tasks take the hours.

Nuha Consulting makes clients' lives easier by automating those tasks. We set up the repeatable work to run on its own and measure the result in hours saved.

Who we work with

Marketing teams and growing companies

  • Heads of marketing whose teams still do their own publishing and follow-up.
  • Managing directors of SMEs where a few people handle marketing alongside other jobs.
  • [Sectors served, to be listed once the first engagements are complete]

How we help

Deciding what to automate

We map the process first

We sit with the marketing team and list each manual task, who does it and how often. We automate nothing we have not seen.

We automate only what repeats

A task qualifies when it repeats every week in the same steps and takes hours the team can count. If the process is still changing, we wait.

The client's team owns the system

Each automation comes with written notes. The team can then change a message or a schedule without calling us.

Our approach

How an engagement runs

Every engagement has four stages.

  1. 1

    Strategy session

    We go through the team's week with them, then take five baseline figures, such as dormant contacts and the reply time to a test enquiry.

  2. 2

    Proposal and approval

    The proposal ranks the processes to automate and puts a figure on each, in hours saved and in output. We build nothing until the client approves.

  3. 3

    Implementation and handover

    We build the automations, then document the system and hand it over so the client's team owns it.

  4. 4

    Day thirty measurement

    At day thirty we take the same five figures again, including the team's manual hours. The difference is the result.

The client signs off the baseline before we build and can check the result against their own records.

A typical engagement runs [X] weeks from strategy session to handover. From day thirty the client's team runs it. [support arrangement after handover, to be confirmed].

Selected results

Earlier marketing results

One of our founders led this work before Nuha. We describe the clients by type only.

Acquisition cost down about 95%

How a tech platform cut its acquisition cost by about 95%

The platform was paying for clicks from users who didn't stay. It partnered with organisations that already reached its one engaged group, and users went from 50 to over 1,000 in a month.

4.4 stars on Google

How a restaurant built a base of regular customers

Customers came once and did not return. The owners moved their spend from acquisition to retention, and the restaurant now has 4.4 stars on Google, a base of regulars and a second location in planning.

From 0% conversion

How an e-commerce brand fixed 0% conversion without a redesign

The founder wanted a redesign, but the analytics showed almost nobody reached the site. The brand moved to a faster platform, built a targeted ad funnel and took conversion from 0% to a healthy rate.

Market data in 24 hours

How a strategy firm got market data in 24 hours

Scraping, bought lists and cold calls had all failed to produce data on small offline businesses. The firm went in through the referral network of the people those businesses deal with every day, had the data in 24 hours and closed the deal.

All client results

Insights

Our latest thinking

[Sample titles, to be replaced with published pieces]

AutomationWhy quote follow-up is usually automated first[Month YYYY]
Marketing operationsWeekly campaign reports without the manual work[Month YYYY]
Data and CRMThe next meetings are in contacts untouched for twelve months[Month YYYY]

All insights

Discuss one process on a first call

On a first call we take one task the marketing team does by hand and say whether it is worth automating.

Our services

We automate repeatable work for marketing teams and SMEs

Our work falls into four areas: marketing, sales, customer experience and business operations. Every system we hand over is documented and the client owns it.

How we help

A marketing team answers enquiries, chases quotes, publishes posts, asks for reviews and writes the monthly report. Most of it repeats every week.

We help marketing teams automate that part in the tools they already use, and a person checks only the exceptions.

Our background covers marketing and the technical side, so we judge each process on the hours it saves and what it produces.

Marketing automation

We set up content drafting, social publishing, email, paid ads, SEO checks, lead capture and campaign reporting. Posts go out on schedule and nobody compiles the weekly figures by hand.

  • Posts cut from one recording
  • Social posts from a queue
  • Email sequences and newsletters
  • Paid ad rotation
  • Scheduled SEO checks
  • Leads into the CRM
  • Weekly campaign report
  • Alerts when a form breaks
See marketing automation

Sales automation

For sales we automate lead qualification, CRM updates, outreach, follow-ups, appointment booking, quotes and pipeline stages, so no enquiry or quote sits unanswered.

  • Qualifying questions before the call
  • CRM records kept current
  • Outreach that stops on reply
  • Quote follow-up until reply
  • Booking link in every reply
  • Quotes drafted from enquiries
  • Deals moved along the pipeline
  • Missed calls answered by text
See sales automation

Customer experience automation

Onboarding, chatbots, support routing, review requests, feedback surveys, upselling and win-back run on their own once we set them up. Each customer gets a welcome when they accept a quote and a message if they go quiet.

  • Welcome and intake on acceptance
  • Chatbot for routine questions
  • Support routed by type
  • Review request after each job
  • Short survey on completion
  • Offers matched to past purchases
  • Renewal reminders
  • Win-back for lapsed customers
See customer experience automation

Business operations automation

We connect invoicing, reporting, data entry, approvals, employee onboarding, scheduling and document generation to the systems the company already runs, so staff enter data once and an AI assistant handles routine internal requests.

  • Invoice sent on acceptance
  • Month-end report filed automatically
  • Data entry from one source
  • Sign-offs routed and chased
  • Employee onboarding checklists
  • Scheduling with reminders
  • Documents built from records
  • Systems connected without rekeying
  • AI assistant for internal requests
See business operations automation

How we start

Before the proposal

  1. 1

    Test enquiry and strategy session

    Before the first call we send a test enquiry through the client's website form and time the reply. In the strategy session we list what the team does by hand, by whom and how often.

  2. 2

    Five baseline numbers

    We confirm five numbers with the client: dormant contacts, contacts untouched for twelve months, meetings booked from the database in the last ninety days, the reply time to three test enquiries sent at different hours, and the team's own estimate of manual hours a week.

  3. 3

    A ranked proposal

    The proposal ranks the processes and puts a number on what the team gets back from each one, and we start building once the client approves it.

From there every engagement runs the same way: proposal, approval, build and handover, then the same five numbers again at day thirty. See our approach

What we do not do

  • We do not build or redesign websites.
  • A task that still changes every week can't run on its own, so we wait until it settles.
  • We do not run campaigns or manage channels. Those stay with the client.
  • We propose automating a task only where the strategy session has shown it costs time or revenue.

Start with one process

On a first call we pick one thing the client still does by hand and put a figure on the hours automating it would save.

Marketing automation

We help marketing teams and SMEs put content, social posts, email, paid ads and the weekly report on a schedule, so the work runs without manual effort.

What marketing teams still do by hand

The marketing teams we work with do the same jobs every week: someone writes the posts one at a time, builds the newsletter from scratch, resizes ad creative for each placement and pulls the numbers from several logins. Those jobs slip whenever anything else comes up.

Once that work runs on its own, the team reads and approves drafts, and the hours that come back go on planning the next campaign. We decide with the marketing team what to automate first and what can wait.

What we automate

  • Content creation

    What runs on its own

    We set up a library that files photos and recordings by campaign and places each in a locked brand template with a caption from approved phrases. Video software cuts long recordings into subtitled clips.

    What the team gets back

    The team reviews drafts already on brand.

  • Social media publishing

    What runs on its own

    We set up a scheduler that publishes from an approved queue at set times, and buying questions in comments and messages become CRM leads. Routine questions about hours or prices get a standard reply.

    What the team gets back

    Publishing carries on in a busy week.

  • Email marketing

    What runs on its own

    We set the email platform to send a welcome series on sign-up and a message to contacts who've gone quiet. Seasonal campaigns sit ready in the queue. Each month the platform drafts the newsletter from recent posts.

    What the team gets back

    Every new contact gets the same welcome, and the newsletter goes out on the same day each month.

  • Paid ads

    What runs on its own

    A design tool with a brand kit produces every placement from one master design. We set ad platform rules that pause a version once its frequency or cost per enquiry passes an agreed limit. Spend then moves to the next version.

    What the team gets back

    Nobody watches the ad account or resizes creative by hand.

  • Search engine optimisation

    What runs on its own

    We track weekly positions for the agreed search terms, and a site monitor flags pages that return errors or drop out of the index. A writing tool drafts pages for those terms.

    What the team gets back

    A broken page shows up within days.

  • Lead generation

    What runs on its own

    We route each website form, ad lead form and social message into the CRM with its source, then send a booking link back at once. Anyone who abandons a form gets a follow-up from where they stopped.

    What the team gets back

    No enquiry waits for an inbox check.

  • Campaign reporting

    What runs on its own

    We join ad spend, enquiries by source, list growth and won deals into a Monday summary against the prior week. An alert goes out when enquiries stop or spend jumps.

    What the team gets back

    The figures arrive every Monday with no dashboard to open.

Deliverables

  • A map of the marketing work now done by hand, with who does it and how often
  • Five baseline figures confirmed with the team before we build anything, and measured again at day thirty
  • The automations, built in the team's own tools and documented so the team can change them
  • A content queue and approval flow showing what publishes when and who signs it off
  • A weekly reporting view: enquiries by source, spend, cost per enquiry and list growth
  • A handover session, after which the team runs the system

Where it fits

  • A marketing team that publishes and reports by hand and has little time left to plan
  • An SME where marketing sits with a small team alongside other jobs
  • A company that runs paid campaigns but resizes creative and rewrites copy for every launch
  • A subscriber list nobody emails
  • Weekly numbers gathered by hand

Client results

[Case study: first marketing automation engagement, day-30 figures]

The challenge

[One sentence on the marketing work the team was doing by hand and the five baseline figures captured before the build]

The solution

[One sentence on which processes were automated first and in what order]

The impact

[Day-30 figure: hours a week returned to the team, set against the five baseline numbers]

What a first call covers

We start with the task that costs the most hours and check whether it is stable enough to run on its own.

Sales automation

We help marketing teams and SMEs automate the work between an enquiry and a closed deal: qualifying leads, following up, booking meetings, sending quotes and updating the CRM.

The work between an enquiry and a deal

Enquiries arrive by web form, phone, email and social message. Someone types each one into a spreadsheet, answers it at the next inbox check and follows up when they remember. Quotes sit until they expire. Few teams count the hours spent retyping details already on record.

We automate that part. Each enquiry gets a reply on arrival and a few qualifying questions before the first call. Follow-up runs until the contact answers or declines, and deals move stage as quotes go out and invoices are paid.

What we automate

  • Enquiry capture

    What runs on its own

    Each web form, email, missed call and social message becomes a CRM record, and a reply with a booking link goes out by email or SMS.

    What the team gets back

    Each contact hears back at once, whatever the hour.

  • Lead qualification

    What runs on its own

    We add a few questions to the form, so need, budget and timing reach the CRM before the first call. Leads go to the right person, and work the company doesn't do gets a polite decline.

    What the team gets back

    Calls start from facts already on the record.

  • Follow-up sequences

    What runs on its own

    We set up a short email and SMS sequence for any enquiry the contact hasn't answered after an agreed number of days, and for any open quote. Both stop on a reply or a booking.

    What the team gets back

    No enquiry or quote is lost to a missed follow-up.

  • Appointment booking

    What runs on its own

    We link a scheduler to the CRM so every message carries open times, and the contact gets a confirmation and reminders with a link to reschedule.

    What the team gets back

    The contact picks a time without an email chain.

  • Proposals and quotes

    What runs on its own

    Once a lead answers the qualifying questions, the quote drafts itself from the record at list prices. The team checks and sends. Online acceptance raises the invoice or deposit request and marks the deal won.

    What the team gets back

    Quotes go out the same day, with fewer steps before payment.

  • Outreach sequences

    What runs on its own

    A sequence from a named sender, with a booking link, goes to a CRM list. That might be contacts untouched in twelve months or new prospects. A reply stops the sequence and goes straight to a person.

    What the team gets back

    Meetings come from a list that had gone quiet.

  • CRM updates

    What runs on its own

    We set the CRM to clean each record on arrival: names and numbers standardised, source and value tagged, duplicates merged, near matches flagged. The rules also drop bounces and unsubscribes and log the consent basis and date.

    What the team gets back

    The team keeps one record per person and never runs a clean-up day.

  • Pipeline management

    What runs on its own

    We set deals to move stage when a quote is viewed or accepted, an invoice paid or a job completed. Notes become dated tasks with overdue reminders. A weekly email sends everyone the same figures.

    What the team gets back

    The pipeline stays accurate without manual updates.

  • CRM implementation

    What runs on its own

    Where there is no CRM, or the team never opens it, we set one up around the company's stages, fields and forms, with email and SMS connected. We import existing contacts, deduplicated and tagged.

    What the team gets back

    The team works in one system, with every contact's history in it from the start.

Deliverables

  • A map of who does what between enquiry and deal
  • Five baseline numbers, agreed with the team before the build and measured again at day thirty
  • The automations, built and documented in the company's own CRM, forms, email, SMS, scheduler and quote tools
  • A weekly report of enquiries by source, first response time, quotes sent and won, and meetings booked
  • A handover session, so the team can change a sequence or a template on its own

Where it applies

  • Enquiries get copied into a spreadsheet by hand
  • Web enquiries wait for the next inbox check
  • Quotes are followed up when someone remembers, and many never are
  • The CRM has contacts idle for twelve months and few logins
  • Deals sit in the same stage for weeks

Client results

[Case study: first sales automation engagement]

The challenge

[One sentence on the enquiry volume, the first response time to three test enquiries and the number of contacts untouched in twelve months before the build]

The solution

[One sentence on which of the areas above were built first, in what order, and in which tools]

The impact

[Day-30 figures: first response time before and after, meetings booked from the existing database, hours a week returned to the team]

Tell us what happens to an enquiry

On a first call we trace each enquiry from arrival to a yes or a no. Then we agree which process to automate first.

Customer experience automation

We automate the routine work after a sale: welcome messages, standard replies, review requests and the message to a customer who has stopped buying. We set it up for marketing teams and SMEs, so every customer gets the same attention.

After the sale, most contact still happens by hand

Someone types every welcome message, and review requests go out when somebody remembers. A lapsed customer goes unnoticed until the revenue has gone. Routine replies eat into campaign time.

We tie each step to a CRM event. The welcome goes out when the deal closes and the review request when the invoice is paid, so the team handles only the exceptions that need judgment.

What we automate

  • Customer onboarding

    What runs on its own

    When a deal is marked won in the CRM, we send the welcome with next steps and who to contact, and an intake form collects the contract details.

    What the team gets back

    New customers stop calling to ask what happens next. Nobody types the same details twice.

  • Chatbots and AI assistants

    What runs on its own

    We add an assistant to the site and the inbox that answers questions on hours, pricing, order status and booking from an answer bank the company has approved. Anything else goes to a person with the transcript attached.

    What the team gets back

    Customers get an answer at any hour.

  • Customer support

    What runs on its own

    We route every email, web form and chat request into one helpdesk, which tags it by topic and acknowledges it with an expected reply time. Templates answer the standard cases and a named person takes the rest.

    What the team gets back

    Nothing sits unanswered in a personal inbox, and response times show in one place. Support hours go to the cases no template covers.

  • Review requests

    What runs on its own

    The review link goes out when the invoice is paid or the job is done, with one reminder if nothing appears. After a strong review we ask for one introduction.

    What the team gets back

    Reviews build up because every job ends with a request. Only customers who have just praised the work are asked for a referral.

  • Feedback collection

    What runs on its own

    We send a short survey after each job. A good score leads to the review request, and a poor one goes to a person for a call. New public reviews arrive with a drafted reply and a flag on low ratings.

    What the team gets back

    The survey catches problems before they become public reviews.

  • Upselling and cross-selling

    What runs on its own

    We pick the next offer from purchase history and send it by email or SMS. The accessory follows the main purchase, the higher tier once usage reaches the limit.

    What the team gets back

    Existing customers get the next offer when it becomes relevant. Nobody builds a one-off campaign.

  • Retention

    What runs on its own

    When a service or renewal is due, we send a reminder with a booking link, and the team gets a task if nobody has booked.

    What the team gets back

    Repeat work gets booked from the record.

  • Reactivation of lapsed customers

    What runs on its own

    We set the CRM to find customers whose repeat purchase is overdue. Each gets one message saying what is still on file, such as a quoted price, and how long it holds. No reply alerts the team.

    What the team gets back

    Lapsed customers surface while there is still time to win them back.

Deliverables

  • A map of every post-sale step done by hand, by whom and how often
  • Five baseline numbers, taken before the build and again at day thirty
  • The automations, documented and connected to the CRM, helpdesk, forms and messaging tools
  • An approved answer bank and message templates in the company's voice
  • A dashboard of response times, review counts, survey answers and reactivation replies
  • A handover session, after which the team adjusts the system itself

Where it applies

  • New customers hear nothing between signing and the start of the work
  • Support requests land in several inboxes
  • Review requests go out now and then, so most jobs produce none
  • Most of a large database has had no contact in twelve months
  • Renewals and repeat purchases depend on the customer remembering

Client results

[Case study: first customer experience automation engagement]

The challenge

[One sentence on which steps after the sale were manual, with the baseline figures for dormant contacts, contacts untouched in twelve months and first response time to three test enquiries]

The solution

[One sentence on which processes were automated first, in what order, and what was handed over]

The impact

[Day-30 figures: hours a week returned, first response time before and after, reviews received and customers reactivated]

Discuss what follows a sale

On a first call we list the steps after a sale that someone still does by hand and say whether this is the place to start.

Business operations automation

Marketing teams and SMEs still move information between systems by hand. We help them run invoicing, reporting, approvals, onboarding, scheduling and integrations without manual effort.

The administrative work around marketing

Invoices go out in a batch at month end. Someone builds the weekly report from several logins and nobody updates it. Approvals travel by email and get chased in person. Different people type the same customer details into the CRM, the invoicing tool and the contract. None of it takes long, but together it fills hours every week.

Once the automations are in, the invoice goes out the day the job closes and the weekly report arrives without anyone opening a dashboard. Judgment calls go to a person. At day thirty we count the hours saved against the baseline.

What we automate

  • Invoicing and payment reminders

    What runs on its own

    We link the CRM and the invoicing tool. When a deal closes or a job finishes, the invoice goes out on the agreed terms. Reminders follow before and after the due date until the payment arrives.

    What the team gets back

    Month end starts without a backlog.

  • Reporting and dashboards

    What runs on its own

    We connect the CRM, the invoicing tool and the ad platforms to one dashboard. Each week it sends the team and finance a summary of revenue invoiced and collected, jobs completed, enquiries and ad spend, and files a copy at month end.

    What the team gets back

    Nobody logs in to build the numbers.

  • Data entry

    What runs on its own

    We connect the web forms to the CRM and to invoicing. A detail typed once, on a web form or in an email, reaches every system that needs it in the format each one expects.

    What the team gets back

    Nobody types the same customer twice.

  • Internal approvals

    What runs on its own

    We route sign-offs through a workflow tool. Discounts above a threshold, content before it goes live, supplier invoices and leave requests reach the right approver with the details attached. It chases anything unanswered after a set number of days.

    What the team gets back

    Approvals stop travelling by email.

  • Employee onboarding

    What runs on its own

    We build the sequence that starts when a hire or contractor goes into the people system. It requests accounts, orders equipment, sets the first-week calendar, sends policy documents for signature and gives the manager a dated checklist.

    What the team gets back

    The manager's checklist arrives already dated.

  • Scheduling and reminders

    What runs on its own

    We connect a scheduler to the team's calendars and the people system. It books site visits, supplier meetings, interviews and internal reviews, then sends confirmations and reminders. The booker can move the slot, and the outcome goes on the record.

    What the team gets back

    The scheduler books site visits without a round of emails.

  • Document generation

    What runs on its own

    We set up a document tool that builds proposals, contracts, statements of work, job sheets and monthly client reports from the CRM record and the approved templates. Each one goes for signature or to the right folder.

    What the team gets back

    Every document goes out with the signed-off wording and the current figures.

  • Integrations between systems

    What runs on its own

    We connect the team's tools (CRM, email and SMS platform, invoicing, forms, scheduler, spreadsheet) through a workflow tool. When an invoice clears, the deal shows as paid, and a price change in the master sheet reaches the website and each listing.

    What the team gets back

    The master sheet is the only place anyone edits a price.

  • AI agents and internal workflows

    What runs on its own

    We build AI assistants and internal workflows for the repetitive tasks that remain. One drafts replies to routine enquiries from the approved answer bank, and another answers staff questions about policy from the company's own documents.

    What the team gets back

    The team reviews drafts and exceptions and can change any workflow itself.

Deliverables

  • A map of the manual work: who does it, how often and how long it takes
  • The baseline measures, agreed before the build, including the team's own estimate of manual hours per week
  • The automations, each with written documentation
  • A monitoring view that alerts the team when an automation fails
  • A handover, after which the client's team owns every workflow
  • A day-thirty comparison against the baseline, including any measure that did not move

Where it applies

  • Payment reminders go out when someone remembers
  • New starters wait for accounts and equipment
  • Proposals start as a copy of the last one and keep its figures
  • Nobody can say which approvals are waiting
  • Finding a time for a site visit takes a chain of emails

Client results

[Case study: first business operations automation engagement]

The challenge

[One sentence on the operational work the team carried by hand and its baseline estimate of manual hours per week]

The solution

[One sentence on which processes were automated first, in what order, and what the team kept]

The impact

[Day-30 figure: hours a week returned, set against the baseline agreed at the start]

Discuss what is entered twice

On a first call we find the detail the team types into more than one system and say what it would take to enter it once.

Client results

Four marketing engagements led by one of our founders

All four predate Nuha. Clients are described by type and not named.

How a tech platform cut its acquisition cost by about 95%

The challenge

The platform bought Google and Facebook clicks, and few of the users they brought in stayed.

The solution

One user group kept coming back, so the platform partnered with the organisations that already reached them, at almost no cost.

The impact

Users grew from 50 to more than 1,000 in a month and marketing spend dropped to almost zero. Acquisition cost fell by about 95%.

How a restaurant built a base of regular customers

The challenge

The owners spent everything on new customers, most of whom came once and never returned.

The solution

The restaurant moved its effort to retention: the dining experience, the service, a local presence and giving regulars a reason to feel the place was theirs.

The impact

The restaurant has 4.4 stars on Google and a steady base of regulars. A second location is in planning.

How an e-commerce brand fixed 0% conversion without a redesign

The challenge

Conversion was 0% and the founder wanted a redesign.

The solution

Analytics showed almost nobody reached the site and social followers weren't clicking through, so the brand moved to a faster platform and built a targeted ad funnel.

The impact

Conversion rose from 0% to a healthy rate without a redesign.

How a strategy firm got market data in 24 hours

The challenge

During due diligence the firm needed market data on small offline businesses. Scraping, bought lists and cold calls had all failed.

The solution

The firm went in through the referral network of the people those businesses deal with every day.

The impact

The firm had its data in 24 hours and closed the deal.

[Case study: first automation engagement, day-30 figures against the five baseline numbers]

The challenge

[The manual work the team was doing and the five baseline figures captured before the build]

The solution

[Which processes were automated first and in what order]

The impact

[Day-30 figures: hours a week returned to the team]

We add each automation case study at day thirty of the engagement.

Discuss one task on a first call

On the call we ask how often one manual task happens and who does it, then say what automating it returns.

About us

A marketing automation consultancy for marketing teams and SMEs

Most marketing teams spend part of every week on work that repeats. We help marketing teams and SMEs automate that work in marketing, sales, customer experience and business operations, then measure the hours they get back.

Who we are

Before Nuha, Muhammad advised marketing teams on strategy and Omar ran the CRM and IT systems those teams worked in, which gives them fifteen years of combined experience in marketing and technology.

In the teams we worked with, much of the week went on tasks that repeat: following up enquiries, updating the CRM, scheduling posts and building the monthly report. None of it needed judgment once the rules were written down.

The software for this now exists. Workflow tools and AI run that work inside the systems a team already uses, but the build fails when the builders know the tools and not the marketing.

Nuha maps the process with the marketing team and automates the tasks that take the longest. After handover the client's team runs it.

The founders

[Photo: Muhammad Hussain]

Muhammad Hussain

Co-founder

Muhammad has spent more than seven years in marketing consulting, advising clients on strategy, branding and digital marketing. His earlier career includes BCG and Dialectica.

His work covers a marketing team's main decisions, including where the budget goes and how customers are kept. The client results on this site come from that work. At Nuha that experience shapes the strategy session and which processes the proposal puts first.

Muhammad works with marketing teams that still build campaigns and reports by hand.

[LinkedIn profile]

[Photo: Omar]

Omar [Surname]

Co-founder

Omar spent four years at IBM in system administration and cybersecurity. He then moved to Novartis, where he worked in business operations, marketing, digital governance and CRM.

At Novartis every integration, permission and data flow had to be documented, and he still works that way. He connects the CRM, forms tool, email, SMS and scheduler. Each write-up goes to the client.

Omar works with companies whose systems are not connected, so staff enter the same data twice and no single record is reliable.

[LinkedIn profile]

Together

Advice and build from the same people

The people who decide what to automate also set it up and write the documentation.

We have automated more than 5,000 hours of manual marketing work. On each engagement we measure the work done by hand before the build and again at day thirty, and the difference is what we report.

How we work

Four rules for every engagement

  • The process first

    Every engagement starts with a strategy session. The marketing team shows us what it does by hand and how often, and we write the process down as it runs.

    We fix an unstable process before we automate it.

  • Where automation pays

    We automate a task when it repeats and its rules can be written down. Someone's time on it also has to carry a cost we can measure, or the task stays manual.

    A service goes into the proposal only when the session has shown the client is losing time or revenue to the problem that service fixes.

  • Five figures, before and after

    Before the build we agree five figures with the client. They cover the state of the database, the reply time to three test enquiries, the meetings booked from existing contacts and the team's own estimate of manual hours a week.

    The proposal puts the biggest loss first. At day thirty we take the same five numbers again and report what has changed.

  • Documentation and handover

    We document each automation as we go. The write-up covers the trigger, the systems it touches, what happens when a customer replies and who in the client's team can change it.

    Handover is a working session with the people who will run it, who can then change or switch off anything.

Our commitments

What clients can expect

Built to the proposal

We test each automation against the proposal before it goes live, then stay on for its first weeks on real enquiries.

The client's needs first

The proposal contains only what the session showed a need for, even when that is less than the client asked for.

The figures as measured

At day thirty we report all five figures. Any that did not move go in too, with the reason as we see it.

The first call

The call covers one process the team runs manually and whether a strategy session is worth booking.

Insights

Our thinking on automation for marketing teams and SMEs

Each piece takes one process we saw a marketing team do by hand and says what changed once it ran without manual effort. We write for heads of marketing, marketing managers and SME managing directors.

[Sample titles and dates, to be replaced with published pieces]

AutomationWhy quote follow-up is usually automated firstFew teams follow up quotes that get no reply. A short CRM sequence takes over and stops the moment the customer answers, so nobody keeps a reminder list.[Month YYYY]
Marketing operationsWeekly campaign reports without the manual workA scheduled report pulls the figures from the ad platforms and the CRM: enquiries by source, spend per enquiry, quotes sent, quotes won. Nobody assembles them by hand.[Month YYYY]
Data and CRMThe next meetings are in contacts untouched for twelve monthsMost CRMs we open hold contacts untouched that long. A reactivation sequence writes to them and routes replies to a scheduler, so meetings come in before the client pays for a new lead.[Month YYYY]
StrategyThe marketing team decides what to automate firstThe order depends on where enquiries go unanswered and which reports anyone reads, and the marketing team knows both. The tool comes after.[Month YYYY]
AutomationWhy we document every automation we hand overThe handover note names the trigger, then describes each step in the tools the automation runs in. The client's team can change any step without us.[Month YYYY]

Talk through one of these processes

If a marketing team still does any of these by hand, we go through it on a first call and say how much of it could run on its own.

Five numbers to capture before automating a marketing process

Before we automate anything we write down five numbers with the client, from dormant contacts to the team's own estimate of manual hours a week. At day thirty we take the same five again, and the gap between the two readings is the result we report.

[Author: one of the founders][Month YYYY][X] min read

Measuring first

[Article body: two or three paragraphs]

Where the five come from

[Article body: two or three paragraphs]

What changes by day thirty

[Article body: two or three paragraphs]

The client confirms all five figures before the build and reads the same five again with us at day thirty.

Related

Why quote follow-up is usually automated first

[To be published]

The next meetings are in contacts untouched for twelve months

[To be published]

Talk through one of these processes

If a marketing team still does any of these by hand, we go through it on a first call and say how much of it could run on its own.

Contact us

Get in touch

Please tell us which marketing tasks your team does by hand, and we will say which to automate first.

What happens on a first call

We take one task your team does by hand and work out who does it, how often, and what it needs to run on its own. One of the founders takes the call.

Book a call (opens in a new tab)
Email[Email address]

We respond within 24 hours.

[Form delivery to be connected; submissions are not yet sent]

Legal

Privacy notice

Last updated: [Date]

[Privacy notice to be added. It should cover the contact form (name, work email, company and message), the email updates form on Our insights (email address), the booking link, which opens a third-party scheduling service, and the web fonts loaded from a third-party font service. It should state how long each is kept, who can see it, and how to ask for it to be removed.]