GTM ENGINEERING · BUSINESS AUTOMATIONBuilt, tested, documented, and handed over to your team.Find your starting point ↗

GTM ENGINEER · BUSINESS AUTOMATION

Spend less time
chasing the
next step.

I build the systems that get the next step to the right person: lead routing, follow-up, account research, and lifecycle rules. Tested, documented, and run by your team.

Erik Lignell | GTM Engineer Sandhi Automation · Dallas–Fort Worth

A WORKFLOW WITH AN OWNERIllustrative flow
01
A new inquiry arrives

Your existing form captures the request.

02
Confirm receipt and assign it

An approved acknowledgment goes out. The responsible person gets the task.

03
Make the next action visible

A callback task stays in view, including when no one has claimed it.

04
Your team takes the conversation

A person reviews the request and responds. Follow-up stops under the agreed rules.

↓ Start with one agreed scenario and your existing software.

MARKETS I’VE WORKED INSIDE

Your system gets built around how your customers actually buy, not a generic template.

  • B2B SaaSNearly four years marketing B2B software to heavy-duty repair shops and fleets
  • Recruiting & StaffingSourcing and market-data tools for finance recruiting
  • DTC E-CommerceDigital products, from the build to the storefront
  • EdTech & K–12GTM systems built at an EdTech marketing agency
  • Libraries & Academic PublishingLead routing delivered for a reference-database publisher

FOR B2B SALES AND MARKETING TEAMS

Build the systems behind
your next sales conversation.

  • Account research and qualification with dated sources
  • Lead routing, enrichment, and CRM handoffs
  • Lifecycle rules: entry, exit, scoring, and suppression

THREE PLACES TO START

What keeps getting
stuck in your business?

Start with one process and a clear owner. We check what your current software can already do, then agree on the useful work to build.

01 · NEW INQUIRIES

Respond to new
inquiries faster.

Send an approved acknowledgment, assign the responsible person, and create a callback or next-action task. Keep unclaimed inquiries visible so someone can take ownership.

What this can include

Booking handoffs, relevant lead context, and meeting-preparation briefs. The acknowledgment confirms receipt; your team still owns the human sales response.

A clear owner and a visible next action

02 · FOLLOW-UPS

Keep follow-ups
moving.

Set reminders or approved messages for unanswered inquiries and open quotes. Give each next step an owner, with stop rules when someone replies or the opportunity closes.

What this can include

After-meeting action items and human-reviewed drafts; revisiting old inquiries when a real reason changes; event or webinar follow-up; reply alerts and queues for teams already doing outbound. Each engagement covers one agreed scenario.

Agreed reminders, ownership, and stop rules

03 · FINDING NEW CUSTOMERS

Find relevant companies
to approach.

If your customers are other businesses, get a research workflow your team can run. Receive reviewed accounts, dated sources, why an event may matter, roles to investigate, and useful next actions.

What this can include

Hiring and leadership changes, past contacts moving to new roles, and public records like permits, registrations, and procurement notices. A signal is a reason to look closer, not proof of a need.

Reviewed evidence and a reason to investigate

CUSTOM BUSINESS AUTOMATION

Have a different process slowing you down?

If your team keeps copying information between systems, chasing updates, or repeating the same administrative steps, we can explore a workflow built around your process.

Examples include new-client onboarding, recurring reports, project handoffs, customer-record updates, and internal reminders.

Discuss your process

MORE WAYS TO MOVE WORK FORWARD

Explore ten
practical workflows.

Picture fewer loose ends: inquiries with an owner, follow-ups with a next step, and job details ready for review. Scroll through ten workflows that could help your team keep work moving.

WORKFLOW 01 / 10

Lead routing and assignment

WHAT IT DOES

Send each website inquiry into your CRM, assign it by service or territory, and create a next-action task. Unmatched inquiries go to a review queue.

WHY IT HELPS

Give every inquiry a clear owner and next step. Your team can see what needs attention without sorting through an unassigned queue.

Discuss this workflow → Lead routing and assignment

WORKFLOW 02 / 10

Inquiry acknowledgement and callback queue

WHAT IT DOES

Send an approved acknowledgement when a new inquiry arrives, and assign a callback task to the office. Flag requests that still have no owner.

WHY IT HELPS

Confirm receipt while making the human follow-up visible. The acknowledgement does not replace a sales response; your team owns the callback and conversation.

Discuss this workflow → Inquiry acknowledgement and callback queue

WORKFLOW 03 / 10

New-client onboarding

WHAT IT DOES

Turn an accepted proposal or signed agreement into a project, assign onboarding tasks, and track missing prerequisites.

WHY IT HELPS

Give the team a shared starting point for each new client. Missing information stays visible before it holds up the next step.

Discuss this workflow → New-client onboarding

WORKFLOW 04 / 10

Estimate follow-up

WHAT IT DOES

Create a follow-up task or approved reminder when an estimate is sent. Stop follow-up when the customer replies, accepts, or declines.

WHY IT HELPS

Keep open estimates in view without relying on someone to remember each one. Stop rules keep the sequence aligned with the customer’s response.

Discuss this workflow → Estimate follow-up

WORKFLOW 05 / 10

Approved-job preparation checklist

WHAT IT DOES

Create a checklist when a job is approved: deposit, materials, customer instructions, and scheduling prerequisites. Keep missing items visible to the office.

WHY IT HELPS

Let the office see what is ready and what still needs attention. Give preparation work a clear place before scheduling moves forward.

Discuss this workflow → Approved-job preparation checklist

WORKFLOW 06 / 10

Stalled-lead and deal reminders

WHAT IT DOES

Find open leads or opportunities without a next action, assign a task, and give the owner a daily exception list.

WHY IT HELPS

Show the owner where a conversation has lost its next step. The daily list gives the team specific items to review and act on.

Discuss this workflow → Stalled-lead and deal reminders

WORKFLOW 07 / 10

CRM cleanup and enrichment

WHAT IT DOES

Standardize agreed fields and enrich company records from approved sources. Flag duplicates and uncertain matches for review.

WHY IT HELPS

Make records easier to use consistently for routing, reporting, and follow-up. Keep uncertain matches with a person instead of treating a guess as a confirmed record.

Discuss this workflow → CRM cleanup and enrichment

WORKFLOW 08 / 10

Past-customer reactivation

WHAT IT DOES

Identify eligible past customers and prepare an approved follow-up sequence. Stop it on replies, opt-outs, or an active sales relationship.

WHY IT HELPS

Give your team a defined way to reconnect with past customers. Eligibility and stop rules help keep the sequence from interrupting an existing conversation or ignoring an opt-out.

Discuss this workflow → Past-customer reactivation

WORKFLOW 09 / 10

Buying-signal research digest

WHAT IT DOES

Scope a build to monitor one defined event, such as a relevant job opening. Deliver a source-linked list of accounts, contacts to investigate, and suggested next actions.

WHY IT HELPS

Give research a defined starting point and evidence the team can check. A signal is a reason to investigate, not proof of budget, urgency, or purchase intent.

Offered as a scoped build, not a validated operating feed.

Discuss this workflow → Buying-signal research digest

WORKFLOW 10 / 10

Invoice-readiness checklist

WHAT IT DOES

When a job is completed, create an office review task showing whether approved scope, parts, time, and required information are complete.

WHY IT HELPS

Bring missing information into view before the office prepares an invoice. This supports human review; it does not approve accounting entries or assure invoice accuracy.

Discuss this workflow → Invoice-readiness checklist

CUSTOM BUILDS

When no tool fits the job, I build it.

Describe the problem in plain words. I turn it into a scoped build at an agreed price, test it on real data, and hand over something your team can run.

DATA PRODUCTS

Turn public data into something you can sell or act on

Reports, benchmarks, and target lists built from government and other public datasets. Every figure keeps its source and date, and missing data shows as missing instead of a guess.

INTERNAL TOOLS

Tools shaped around how your team works

Research, sourcing, and analysis tools for a specialist team, like a recruiting desk or a sales team, that put results straight into the systems you already use.

DIGITAL PRODUCTS

E-Commerce products and the store that sells them

Mini SaaS apps, interactive dashboards, and calculators built from code, with the math checked independently, plus the storefront and checkout that sell them.

HOW A CUSTOM BUILD WORKS

From a plain-English problem to a tool your team runs.

Describe what you need
  1. 1Describe

    Tell me the job in plain words, with a real example.

  2. 2Scope

    We agree what it does, what it won’t, and the price.

  3. 3Build and test

    Built and tested on your real data, including the edge cases.

  4. 4Hand over

    Documentation and a walkthrough, so your team can run it.

AI ENABLEMENT

Get your team using
AI on real work.

You’re probably already paying for the licenses. What your team needs now is a process: which tasks to start with, what context the AI needs, and what someone checks before anything ships.

01 · START WITH THE WORK

Pick the first workflows

We map the tasks your team repeats every week and choose the few where AI saves real time and the output is easy to check.

02 · SHARED CONTEXT

Set up the workspace

Shared projects loaded with your documents, brand voice, and instructions, so everyone starts from the same context instead of a blank chat.

03 · YOUR OWN KNOWLEDGE

Build internal knowledge tools

An assistant that answers from your own playbooks and manuals, and says so when the answer isn’t in them.

04 · TRAINING BY ROLE

Train people, with review built in

Sessions for leaders and for the people doing the work: prompting, projects, data rules, and what to check before anything goes out.

WHERE I’VE DONE THIS

An EdTech marketing agency, company-wide

The company had AI licenses, but most use was basic writing help. I started by showing working dashboards in client calls, then built an answer engine over six internal field manuals, set up workspaces for leaders, and ran training and a bootcamp once people asked how the work was made.

  • The team moved onto shared projects for copywriting, research, and client prep
  • Leaders got their own workspaces and training
  • Useful examples came first; training followed demand

Adoption is described from observed behavior. It was not a measured before-and-after productivity study.

SELECTED WORK

I build the systems that keep your company moving.

Three examples: lead routing for a publisher, lifecycle rules, and a research workflow that attaches the source to every account. Open one to see the problem, what I built, and what the evidence supports.

3 selected projects
REVENUE OPERATIONSSHIPPED

Lead routing + AI enrichment

Replace an unowned form queue with enriched leads, territory-based assignment, and a clear acknowledgment.

Client delivery · Reference-database publisher · 2026
ZapierGoogle SheetsGPT-4o-mini
LIFECYCLE & REVOPSSHIPPED

Nurture & lifecycle architecture

Give every contact clear entry, exit, and suppression rules across sales, onboarding, and marketing.

Prior role · Fullbay · 2022–2025
Marketo EngageLead scoringCRM sync
SIGNALS & QUALIFICATIONSHIPPED

Signal radar

Find companies describing a problem in public. Qualify the account and carry the source into outreach.

Internal · Partner In Publishing · 2026
Claude CodeTrigify MCPApollo

HOW IT WORKS

Map the task.
Build the workflow. Hand it over.

We agree on the behavior before building, test the exceptions,
and make sure your team can operate the result.

THE PROCESS MAPAgreed before building
TriggerWhat starts the workDefined
Next actionWhat should happenAgreed
OwnershipWho takes the next stepNamed
ExceptionsWhat needs human reviewVisible

Start with a real process and a useful change.

01 · MAP THE TASK

Agree on what
should happen next.

Walk through a recent example. Identify the trigger, current tools, owner, and the point where work waits or gets copied by hand. Check the software’s existing features first.

  • One agreed scenario and responsible person
  • Clear rules for the normal path and exceptions
  • Representative examples and acceptance criteria

In the routing project, a territory lookup table kept changing assignments editable.

START WITH A BOUNDED BUILD

Simple workflow builds
from $1,000.

One agreed workflow, up to two existing business apps, and three agreed decision rules. A clear scope before work begins.

What the starter includes

  • A process map and representative tests
  • A configured workflow with exception handling
  • A written handoff and team walkthrough
  • One scoped revision
  • Seven days of defect fixes after acceptance

Define the scope first

We define the trigger, next action, responsible person, and behavior for missing information, duplicate events, replies, closed opportunities, and errors.

Client-approved software fees are separate. Larger builds, research workflows, and optional ongoing support are quoted separately. The $1,000 starter can cover custom automation when it fits these same bounds.

Book a call ↗
Erik Lignell

Erik Lignell | GTM Engineer

Sandhi Automation

Dallas–Fort Worth, Texas
Connect on LinkedIn

ABOUT

Get workflows that fit your team.

My background spans 15 years across marketing and automation in B2B SaaS, EdTech, and agencies, including eight years running an independent automation consultancy.

At Partner In Publishing, I built an ABM platform from zero, delivered client automation systems, and led company-wide AI enablement. At Fullbay, I built lifecycle programs and coordinated campaigns across seven departments.

Partner In PublishingGTM Automation Engineer · 2025–2026FullbaySenior Email Marketing Specialist · 2022–2025

TOOLS I’VE BUILT WITH

ClayHubSpotSalesforceClaude CodeCodexInstantlyMarketon8nZapier

BEFORE WE BUILD

Let's set clear expectations.

Bring a recent example of the process that keeps getting stuck.

Book a call ↗
Do I need to know anything about automation?

No. Show me what happens today, who does each step, and where the work gets delayed. We map that process in plain language before deciding what to configure or build.

Will I need new software?

We start with your existing software and its native features. A useful change may be configuration and training. If another tool is needed, you approve its separate cost before it is included.

Do you respond to leads or run our sales campaigns?

I build, test, document, and hand over the workflow, then train your team. An automated acknowledgment confirms receipt; your people own the sales response and conversation. This is not an outsourced sales department or ongoing campaign operation.

What happens when someone replies or a quote closes?

We agree on stop rules and test them. Replies, closed opportunities, missing information, and errors must go to the right person or stop the relevant follow-up. Your team approves any automated messages.

What happens after handover?

The starter includes a walkthrough, one scoped revision, and seven days of defect fixes after acceptance. Optional ongoing support or additional workflows require a separate scope. No revenue, conversion, or universal response-time result is promised.

START WITH ONE PROCESS

What keeps blocking
your success?

Bring a recent inquiry, open quote, or repeated task.
We’ll work out whether a small workflow can help.