Prepare an account brief.
Collect a company's product and service pages. Keep the original URLs with the material your team reviews before a call.
ACCOUNT RESEARCHMAKO / WEBSITE RESEARCH API
Turn public web pages into Markdown and structured source material for account research, client briefs and AI workflows. Start by inspecting the actual output.
No signup for this sample. Your own run uses your Apify account.
01 / OPEN THE OUTPUT
Switch between two real pages and three output views. Everything below is a saved extraction, ready to inspect and download.
Showing Markdown for Mako home.
GTM ENGINEERING FOR B2B SAAS
# Good signals.
Better systems.
Your next move.
I build the research, outbound and CRM workflows behind your sales process. Clear context for your team. Less work between the tools.
[Book a 15-minute fit call](https://cal.com/mako-gtm/15min)[Explore the builds](https://makorev.com/#projects)
Built with Valdeir Lima.
**Based in Ireland. Working globally.**
THE GTM SYSTEM01 / 03
Hover or tapTap a signal. Follow the flow.
RESEARCH & QUALIFY
### Context before contact.
ACCOUNT BRIEFFor review
HIRING SIGNAL
A growing team. A useful opening.
Why this account?
A SaaS team hiring in GTM
What changed?
Role, requirements & source
What happens next?
Offer help while they hire
Illustrative workflowYour team makes the next move.
BUILT WITH YOUR STACK
The right tools. Connected around your workflow.
Explore what each tool brings
**Clay**Bring company research, contact enrichment and qualification into one table.
Data & research
A stack shaped by the job. We agree on the tools and access before the build.
01 / WHAT I BUILD
## The work between
your tools. Handled.
You have a product to sell. Mako builds the research, outreach and CRM workflows around your next stage of growth.
01
### Signals & outbound
Find the accounts worth a conversation. Connect public buying signals, account research and enrichment to a considered outreach process.
FROM SIGNAL TO CONVERSATION
- Signal sourcing & account research
- Qualification & enrichment
- Outreach preparation & review
02
### CRM & revenue operations
Give your sales process a reliable foundation. Connect the tools, clean up the handoffs and make the next step clear for every account.
FROM SCATTERED DATA TO A CLEAR NEXT STEP
- Lead routing & lifecycle stages
- CRM integrations & data hygiene
- Workflow monitoring & reporting
03
### AI & custom automation
Put repetitive work into a workflow your team can inspect. Use AI for research, preparation and updates, with review where judgment matters.
FROM MANUAL TASK TO REPEATABLE WORKFLOW
- Account research & call preparation
- AI-assisted qualification
- Custom scrapers & API integrations
02 / SELECTED WORK
## Built to be useful.
Open to inspection.
My own engineering projects and fictional-data demonstrations. See what I built, how I checked it and where the evidence stops.
[01 / INDEPENDENT PROJECT
### One reply. A shared stop.
Keeping email and LinkedIn follow-ups consistent after a reply is retrieved and matched in my own outreach system.
Identity matching · Supabase · n8n · Failure handling
Read the engineering case](https://makorev.com/portfolio/cross-channel-reply-stops) [02 / FICTIONAL DATA DEMO
### Lead checks before the CRM.
Eight sample records become two prepared payloads and six visible exceptions. Local tests; no CRM connected.
Data quality · Batch deduplication · n8n workflow
Read the preparation case](https://makorev.com/portfolio/crm-preparation)
SUPPORTING PUBLIC WORK
[View Valdeir’s portfolio](https://makorev.com/portfolio)
[
DATA & SIGNALS
### A custom research toolkit.
Published Apify tools for collecting structured research data. The Web Content Crawler listing includes its inputs and sample output.
Apify / Data collectionView published Apify tool ↗
](https://apify.com/agency-shift/web-content-crawler)[
AI WORKFLOWS
### Repeatable work, encoded.
Open-source Claude Code skills for marketing, content and creator operations. Practical instructions and workflows you can read and adapt.
Claude Code / Automation / Open sourceRead the skill files ↗
](https://github.com/agency-shift/agency-shift-skills)[
ENGINEERING EXPERIMENT
### Content production as code.
A code-based motion graphics workflow for LinkedIn, combining HTML, CSS and frame-by-frame rendering to make content production repeatable.
Node.js / HTML & CSS / ffmpegExplore the source code ↗
](https://github.com/valdeircs/linkedin-motion-rig)
03 / HOW WE WORK
## Start with one
workflow that matters.
A focused build gives you something concrete to use, evaluate and improve. We agree on the scope and how success will be checked before implementation.
[Discuss your workflow](https://cal.com/mako-gtm/15min)
01
### Find the friction
Map the workflow, the people and the tools. Choose one bottleneck worth fixing.
02
### Define the build
Agree on the inputs, deliverables, cost and acceptance criteria. Set the review points.
03
### Build & validate
Connect the system, test real examples and handle the edge cases with your team.
04
### Put it in your hands
Document the workflow and hand it over. Scope any ongoing support separately.
THE PERSON BEHIND MAKO

Valdeir LimaGTM & Automation Engineer
## Work directly with
the person building it.
I’m Valdeir, based in Navan, Ireland. I build practical systems with n8n, Apify, Clay and custom code — from research pipelines to the integrations around your CRM.
Mako is my independent work; some public tools use the Agency Shift name. I’m open to GTM and automation engineering roles, contract work and focused projects.
You work with me from the first conversation through the handover. The aim is straightforward: a workflow your team understands, can inspect and can run.
[Meet me on LinkedIn](https://www.linkedin.com/in/valdeir-lima/)
A FEW PRACTICAL DETAILS
## Before
we build.
Who is Mako a good fit for?
B2B SaaS founders and small revenue teams with a product to sell and a specific operational bottleneck. That might be finding relevant accounts, connecting the CRM or reducing repetitive research. We use the first call to check the problem and whether a focused build is the right next step.
What does the first engagement look like?
We start with one workflow. Before work begins, we agree on its scope, inputs, deliverables, cost and acceptance criteria. The build includes implementation, validation and documentation. Timing depends on the integrations and access required.
Can you work with our existing tools?
Yes. I work with tools including n8n, Clay, Apify and HubSpot, and build custom integrations where useful. We review your current accounts and subscriptions before deciding what to keep, connect or add.
Who owns and operates the system?
The aim is a system your team can operate in accounts you control. Code, workflow configuration, documentation and handover are defined in the project scope. Third-party software remains subject to its own licensing and subscription terms.
Do you guarantee meetings or revenue?
No. I deliver the agreed systems and validate that they work. Commercial results also depend on your offer, market, data quality and sales execution. We agree on useful measures and improve the workflow using actual feedback.
Where are you based?
Navan, Ireland. I work remotely with teams in Ireland, the UK, Europe and the US, with meeting times agreed around our shared working hours. Data sources, access and hosting requirements are agreed before implementation.
LET’S MAKE THE NEXT STEP CLEAR.
## What’s slowing
your GTM down?
Bring one bottleneck.
We’ll explore what a useful first build could look like.
[Book a 15-minute fit call](https://cal.com/mako-gtm/15min)Scope: exactly two supplied URLs. Link following was off. Both returned HTTP 200; neither Markdown output was truncated. This test does not establish whole-site coverage.
Inspect the run summary ↗02 / PUT IT TO WORK
A useful starting point for GTM teams and agencies that need reusable website context.
Collect a company's product and service pages. Keep the original URLs with the material your team reviews before a call.
ACCOUNT RESEARCHUse heading-aware chunks as source material for your own retrieval or assistant workflow. Review the generated answer against the source.
AI GROUNDINGMove the same structured output into a workflow, a research folder or a database, with page metadata and extraction diagnostics intact.
AGENCY WORKFLOWS03 / A WORKFLOW YOU CAN OWN
Start with the example. Then choose your pages, connect your Apify account and collect the context your next research task needs.
Download the n8n workflowImport the JSON into your own n8n instance. Nothing runs from this page.
Tested in n8n 2.41.6: 2 pages → 33 source packets
2 October 2026 · local Docker CLI execution.
Use the two supplied URLs for a small first check. Keep page limits and link following explicit.
Download sample input ↗The setup guide explains credentials and run options. Your Apify account pays for your runs; the sample downloads are free.
Read the n8n setup ↗Read the run summary, page status and source chunks. Handle missing or partial pages before they become a brief or an AI answer.
View the example on GitHub ↗VALDEIR LIMA / GTM & AUTOMATION ENGINEERING
Need selected website pages connected to your research process or CRM? I can scope the integration, review points and handover around the tools your team already uses.
THE PRACTICAL DETAILS
A small, verifiable extraction comes before a larger workflow.
Page URLs, titles, extracted text and links, with optional Markdown and heading-aware chunks. Chunks include source URLs and identifiers. This sample uses markdown-and-chunks; inspect the JSON view for the exact fields returned.
It extracts public static HTML. It does not render JavaScript in a browser or log into websites. Pages that need those capabilities, reject requests or return little HTML can produce incomplete or failed results. Test your own target before scaling.
No. It collects and structures source content. It does not create embeddings, validate the truth of the source, or write answers. You choose the model or retrieval system downstream and review its conclusions.
As checked on 2 October 2026, the Actor's Free-plan base rate is a $0.05 startup event per allocated GB, with a minimum of one event per run. It is not a per-page price. Plan discounts and published prices can change. A maximum-charge setting is a spending ceiling, not a quoted price.
Check current Apify pricing ↗Yes. The public proof contains the input, output and run summary from 2 October 2026 at 13:28 UTC, using build 0.2.2. We used Mako-owned pages so you can inspect the source. Their live content can change after this saved capture.
Download proof metadata ↗