Two days a week
One engineer for one area, such as the CRM and lead flow. Fits companies of 20 to 80 people.
Forward deployed engineering
An engineer inside your team.
You need someone who builds automation and AI systems every week, and a full-time hire does not make sense yet. A Puento engineer works on your priorities, in your tools and channels, and leaves documentation and an owner for everything they build.
In one paragraph
What is forward deployed engineering?
Forward deployed engineering means a Puento engineer joins your team for an agreed period, works in your tools and channels, builds with the people who run the process, and hands every system to a named owner before the engagement ends.
It fits companies of 20 to 300 people without a platform team, when there is more to build than one project can cover.
Key takeawaysTwo or three fixed days a weekTwelve weeks, with an end dateEvery system handed to a named owner
Who it is for
When does an embedded engineer fit?
Good fit
- You have many small automation and AI needs, and priorities change every week.
- Knowledge about the process sits with people, not in documents.
- You need a GTM or AI engineer, but not full time.
- The Technical Diagnostic gave you a long list of things to build.
Better to wait
- You have one clearly described problem and want a fixed budget. A project in sprints fits better.
Compared
Embedded engineer, a full-time hire or a freelancer?
| Question | Full-time hire | Freelancer | Embedded engineer |
|---|---|---|---|
| Start | After recruitment | Fast | After the Technical Diagnostic, or with it in the first three weeks |
| Scope | One person’s skills | One task at a time | CRM, automation and AI in one engagement |
| Documentation and owner | Depends on the person | Rarely in scope | In scope for every system |
| When it ends | When the person leaves | When the task is done | On an agreed date, with a handover |
How it runs
Twelve weeks, from diagnostic to handover
If you have already done the Technical Diagnostic, the build starts in week one.
Weeks1–3
Diagnostic
Audit report and roadmap, and a named owner for each system we plan to build.
Weeks4–10
Build
Fixed days every week, priorities reviewed in a 30-minute call with your lead.
Monthly1×
Written summary
What was built, who owns it and what it costs to run each month.
Weeks11–12
Handover
No new builds. Documentation, runbooks and training for each owner.
Options
Three ways to set it up
Three days a week
One engineer across two or three areas, with architecture review by our technical architect. Fits most companies.
Embedded team
An engineer and a RevOps engineer, when GTM and AI work run in parallel.
Both sides
What you get and what we need from you
What you get
Design and builds across AI agents, RAG systems, automation and GTM engineering, a weekly priority review, a monthly written summary, and documentation, a runbook and training for every system.
What we need from you
One person who sets priorities, a named owner for each system before it is built, access to your tools, and one or two hours a week from the people who run the process.
Proof
Trusted by high-growth teams
“Mateusz has a unique ability to bridge the gap between marketing, sales, and tech. He brings a rare mix of technical acumen and strategic thinking that consistently pushed our projects forward.”
FAQ
Frequently asked questions
Not sure where to start? The Technical Diagnostic is the first step for every build.
How many days a week?
Two or three fixed days a week, agreed before the start. Larger companies can have an engineer and a RevOps engineer together.
How long does it last?
Twelve weeks to start. You can extend in blocks of six weeks. The last two weeks of every period are for handover.
Remote or on site?
Remote, from the kickoff to the handover. The engineer works in your tools and channels during EU working hours.
What if we do not use all the days in a month?
The hours are not lost. You can use them later in the engagement.
What if we need to stop early?
You can end the engagement with notice. The hours you have left can still be used during the notice period, and we use them to hand over what is built.
Who is the engineer?
An engineer from the Puento team, the same person for the whole engagement. Our technical architect reviews what is built.
What happens at the end?
Every system has a named owner, documentation and a runbook. You can stop there, extend, or move to ongoing support, where we act as the second line behind your owner.
Embedded engineer or a project?
A project fits one clearly described problem and a fixed budget. An embedded engineer fits many smaller needs whose priorities change from week to week.
How is this different from staff augmentation?
With staff augmentation, a developer joins your backlog and takes the tasks your team writes. An embedded engineer also finds the work worth automating, agrees the scope with you, and leaves each system documented and owned by someone on your team.
Tell us what slows your team down.
A 30-minute call. We’ll tell you what we’d build first.
What happens next
- 130-min callWe look at your situation and tell you what we would build first.
- 2Technical Diagnostic2–3 weeks, fixed scope: audit report and roadmap.
- 3Build in sprints4–6 weeks each, documented and handed over.