How It Works

How a build works, from scope to handoff.

Fixed scope, most builds in 30 to 45 days. You give focused input at a few points, Empact builds inside the tools you already use, and you leave owning the system.

What to Expect

A clear build without the daily lift.

Timeline

Most builds are completed over 30–45 days. Focused builds may be shorter once the scope is clear.

Your involvement

You give focused input at a few key points. We handle the build, but your feedback helps make sure it fits the way your business actually works.

What you leave with

A working setup your team can use: organized or newly created source material, workflow logic, AI/automation steps, and clear outputs your team can act on.

The Process

How the build works.

Phase 01

Understand

We map how your team works today, where time goes, and where AI can carry the load. Then we define exactly what gets built, what is needed, what access is required, and what success looks like. Nothing gets built until the scope is clear.

Phase 02

Build

Hands-on implementation inside the tools you already use: the connections, workflows, agent logic, review points, and outputs, shaped around your business, brand, and ways of working. The deliverable is a working system, not a set of recommendations.

Phase 03

Hand Off

We walk your team through what was built, how it runs, and how to change it, with documentation and recorded walkthroughs where useful. Then it’s yours to keep. No retainer.

Your Role

Focused input, not constant meetings.

You do not need to manage the build day to day. But we do need the right input at the right moments.

Typical input includes:

  • discovery conversations with the right people
  • access to relevant docs, tools, exports, or source material
  • feedback on criteria, context, and early outputs
  • a final walkthrough so your team knows how to use what was built
Access & Ownership

Built with your context. Owned by your team.

Every build depends on what already exists and what needs to be created. Sometimes that means organizing shared documents, copied files, exports, or access to existing tools. Sometimes it means building missing context first, like criteria, directories, brand guidance, or source material the workflow needs to work properly.

We agree on the tools, access, source material, and recommended setup before work begins, then build the simplest system that can do the job.

You leave with the build, the supporting documentation, and enough understanding to keep using it with confidence.

FAQ

What people ask about the build.

What happens after handoff if something needs more work?

You get two weeks of working together after handoff: we test it with you, take your feedback and adjust. After that, any new work is scoped as its own small project. Because we built the original, there's no starting over. You buy what you need, when you need it, with no ongoing contract.

Who actually does the work?

Alexandra Franco, Empact's founder, leads every build. She has 16 years in B2B marketing and is a Claude Certified Associate - Foundations. Empact is a solopreneur practice with specialists who join when a build needs them. You deal with one person throughout.

Does anything go out without a person checking it?

No. Every build has a review point before anything reaches a customer or goes public: a person says yes first. That's how we build for clients and how we run our own. As a workflow proves itself, you can choose where it needs less checking, but that call stays yours.

Start Here

Not sure if you’re ready?

Tell us where you are, and we’ll suggest the right starting point.

Best fit: founder-led teams running marketing themselves or with a lean team.

Takes about two minutes.

We reply within 1 to 2 business days.