OPS.01
Marketing leadership
A senior operator inside the team. Priorities, cadence, and ownership set weekly — with the numbers reviewed in the same room.
Outcome
Decisions stop waiting on the founder.
SYS.01 — Growth engineering practice
Growth,
engineered.
Transform complexity into structured growth
EDAS Digital embeds marketing leadership, automation, and AI into your operation — turning fragmented tools, manual work, and scattered data into one structured system that scales.
EDAS.SYS
V1.0
Module — docked
01/01
Practice
We build the systems behind high-performing marketing operations.
PRF.02 — Track record
PRF.01
R$0M+
Revenue generated with digital products across launches, evergreen funnels and live events.
PRF.02
R$0K+ / mo
Paid media managed inside a single operation, with reporting built in-house.
PRF.03
0+ attendees
Served by a ticketing and check-in system built from scratch, not bought.
PRF.04
0-figure BRL
Digital products company where the marketing operation was led day to day.
OPS.03 — What EDAS does
Five functions.
One operating system.
Most operations are not short on tools. They are short on structure. EDAS installs the layer that makes the tools behave like one system — and stays until it runs without us.
OPS.02
Automation
Manual handoffs become tracked events. Briefs, approvals, reporting and billing route themselves — no one copies data between tabs.
Outcome
Hours returned to the team every week.
OPS.03
AI systems
Models placed only where they change throughput: research, drafting, classification, QA and summarization inside the existing workflow.
Outcome
Same headcount, more output.
OPS.04
Internal tools
Dashboards, process systems, financial systems, creative management. Built for how your operation actually works, not licensed for someone else's.
Outcome
One place to look for the answer.
OPS.05
Growth operations
Funnels, launches, events and reporting connected end to end. Spend, pipeline and delivery read from the same source.
Outcome
The whole machine becomes visible.
OPS.06
How we engage
Audit first, always. We map the operation before we touch it, then build in the order that removes the most work per week of effort.
Outcome
No rebuild you did not agree to.
SYS.04 — The EDAS system
Six states.
Nothing skipped.
Every engagement runs the same sequence. The order is not a preference — each state produces the input the next one needs.
SYS.01
Audit
Tools, data, handoffs and owners mapped as one diagram.
SYS.02
Bottleneck
Where work stalls, repeats, or waits on one person.
SYS.03
System design
The target state, written down before anything is built.
SYS.04
Build
Tools, dashboards and integrations shipped in build order.
SYS.05
Automate
Manual steps removed one at a time, each one measured.
SYS.06
Scale
Volume rises. Headcount and manual work do not.
Terminal state
The system is done when the operation runs the same way whether or not we are in the room that day.
CASE.05 — Selected work
Systems built,
and what they moved.
Each case follows the same structure: the context, the bottleneck, the system built, the stack, and the result. Open one to read the full record.
Context
An 8-figure BRL digital products company running launches, evergreen funnels and live events in parallel, with a lean internal team.
Bottleneck
Growth outpaced the operation. Media, creative, delivery and finance each kept their own numbers, so every decision started with a reconciliation.
System built
A single operating layer: media reporting pulled to one dashboard, launch calendars and creative pipelines standardized, and finance reconciled against the same source.
Result
R$40M+ generated with digital products, and R$150K+/month in paid media run against one reporting source.
Meta AdsGoogle AdsGA4ActiveCampaignNotionCustom dashboards
Context
A live event with more than 1,000 attendees, sold across several batches and access tiers.
Bottleneck
Off-the-shelf ticketing took a cut, held the customer data, and could not express the tier and batch logic the event actually used.
System built
An in-house platform: checkout, ticket issuing, QR credentials, door check-in, and live capacity by tier — with attendee data landing straight in the CRM.
Result
1,000+ attendees issued, validated and checked in on owned infrastructure. Ticketing fees removed and the attendee list stayed in-house.
Custom checkoutPayment APIQR check-inCRM syncOps dashboard
Context
Leads arriving from paid media, organic, events and partner lists, each landing in a different place.
Bottleneck
A person opened every submission, decided where it belonged, and pasted it forward. Routing happened in business hours only, and attribution was lost on the way.
System built
One intake layer: every source normalized to the same schema, scored, deduplicated, routed by rule, and written to the CRM with its source intact — with failures surfaced instead of silently dropped.
Result
Lead handoff runs without a human step, around the clock, and source attribution survives to the CRM record.
MakeWebhooksActiveCampaignCRM APISlack alerts
Context
A creative team producing ads, pages and launch assets on a weekly cycle for several offers at once.
Bottleneck
Briefs lived in chat, versions lived in drives, approvals lived in inboxes. Nobody could answer what was in production without asking three people.
System built
An internal platform for briefs, versioning, review and approval — with production status, owner and due date on every asset, and performance read back against the creative that produced it.
Result
Creative status is answered by the system, not by a meeting. Approvals are recorded, and performance is tied to the asset that earned it.
Internal appNotionDrive APIApproval flowReporting layer
Context
Six-figure monthly media spend reported separately from the pipeline it was supposed to be producing.
Bottleneck
Weekly reporting was assembled by hand from platform exports. By the time the numbers agreed, they described a week that had already ended.
System built
A reporting layer joining ad platform spend, site behaviour and CRM stages on one key, refreshed daily, with definitions written down so every team reads the same metric the same way.
Result
Spend-to-pipeline is available daily without a manual export, and budget decisions are made on current data instead of last week's.
GA4BigQueryLooker StudioCRM APIAd platform APIs
SRV.06 — Engagements
Three ways in.
Always the audit first.
Every engagement starts by mapping what you already have. What comes after depends on what the map shows.
SRV.01Start here
EDAS Systems Audit
Two weeks. We map your operation end to end — tools, data, handoffs, owners — and rank every place the work stalls.
- System diagram of the current operation
- Ranked bottleneck list with cost per week
- Target-state design
- Build order with effort and sequence
2 weeks · fixed scopeBook
SRV.02
EDAS Growth Retainer
Monthly. We build the system the audit specified, then run it — automations, internal tools, reporting, and the cadence around them.
- Automation and integration build
- Internal tools and dashboards
- Reporting layer and metric definitions
- Weekly operating review
Monthly · rollingEnquire
SRV.03
EDAS Fractional Leadership
Ongoing. Senior marketing and operations leadership inside your team — the decisions, priorities and accountability, without a full-time hire.
- Marketing and operations direction
- Team structure and hiring input
- Budget and media oversight
- Vendor and stack decisions
Ongoing · part-timeEnquire
EDS.07 — Founder
Eduardo Silva
Operator and builder. Marketing, operations and the systems that carry both.
Eduardo has spent his career inside marketing operations, not beside them. He led marketing for an 8-figure BRL digital products company, managed more than R$150K/month in paid media, and built the internal systems the team ran on.
One partner fluent in marketing, operations and systems.
That combination is the point. Strategy without systems stalls at execution; systems without marketing judgment automate the wrong things. Eduardo works in the space most teams leave empty — between the plan, the operation, and the software that has to carry it.
Revenue
Helped generate more than R$40 million with digital products.
Leadership
Led marketing operations inside an 8-figure BRL digital products company.
Media
Managed operations running more than R$150K/month in paid media.
Systems
Built dashboards, process systems, financial systems, creative management tools and a 1,000+ attendee ticketing platform.
Background
Launches, workshops, funnels, events, automation and marketing leadership.
Languages
Fluent in English and Portuguese. Works with teams in the US and Brazil.
Available for audit engagements
DOC.08 — Systems mindset
What we hold to.
01
Growth is not a hack. It's a system.
Tactics expire. The structure that produced them is what compounds.
02
Most teams don't need more tools. They need structure.
Adding software to an unmapped operation buys you a new place to lose things.
03
Automation should remove work, not create more noise.
If a workflow adds notifications without removing a task, it was not worth building.
04
AI is useful when it improves the operation.
We place models where throughput changes and measure it. Everywhere else, it waits.
STK.09 — Capability map
The layers
we work across.
Tools are chosen last, and only after the map. This is the surface area we cover, not a list of logos.
STK.01
Automation
- Make, Zapier, n8n
- Webhooks and queues
- Custom scripts and jobs
- Error handling and alerts
STK.02
CRM
- HubSpot, Pipedrive
- Pipeline and stage design
- Lead scoring and routing
- Deduplication rules
STK.03
Email and lifecycle
- ActiveCampaign, Klaviyo, Brevo
- Segmentation and journeys
- Transactional flows
- Deliverability hygiene
STK.04
Data and reporting
- GA4, BigQuery, Supabase
- Looker Studio, custom dashboards
- Metric definitions
- Attribution modelling
STK.05
Landing pages and web
- Next.js, Webflow, WordPress
- Checkout and payment flows
- Testing and experimentation
- Tracking and consent
STK.06
Operations
- Notion, ClickUp, Slack
- SOPs and process design
- Approval and review flows
- Operating cadence
STK.07
AI
- Claude, OpenAI
- Retrieval over internal docs
- Classification and extraction
- Agents inside workflows
STK.08
Internal systems
- Operations dashboards
- Financial and billing systems
- Creative management
- Ticketing and events
The stack is an outcome of the design, never the starting point. If your operation already runs on something not listed here, we work in it.
OPS.10 — Start here
Let's map
your operation.
A systems audit takes 2 weeks. You leave with a diagram of your operation, a ranked list of bottlenecks, and a build order — whether or not we work together after it.
- 01See the system behind your growth.
- 02Remove the manual work, one step at a time.
- 03Keep the structure after we leave.