AI workflows
Task design, data access, evaluation, permissions, human review, integrations, and failure recovery.
Based in Ericeira · Working across Portugal and Europe
I work directly with founders and small product teams on AI workflows, custom software, integrations, and difficult technical decisions. I am based in Ericeira and work remotely across Portugal and Europe.
Direct answer
I am an independent AI and full-stack product engineer based in Ericeira, Portugal. An engagement can begin with an audit, a bounded delivery, or ongoing technical direction. The location makes contracts, working overlap, and occasional in-person planning within Portugal straightforward; the work itself is designed for remote collaboration and clear written handoffs.
Related work
The capabilities page shows the other ways I can help and the case studies behind them.
When this helps
What the work covers
Each engagement names the decision owner, evidence, delivery boundary, operating responsibility, and handover before implementation expands.
Task design, data access, evaluation, permissions, human review, integrations, and failure recovery.
Web products, internal tools, APIs, data systems, tests, deployment, and a maintainable handover.
Architecture, sequencing, delivery risk, build-versus-buy decisions, and support for the team doing the work.
Evidence-led review of a codebase, system, delivery path, or one decision that has become expensive to guess.
Compare the options
| Engagement | Best when | Boundary |
|---|---|---|
| Focused audit | A consequential decision needs evidence before implementation. | Ends with findings, priorities, and a clear next decision. |
| Defined delivery | One workflow or product path can be scoped from input to release. | Requires a client-side owner for access and product decisions. |
| Fractional direction | Senior technical decisions recur, but a full-time role is premature. | Time and response expectations must remain explicit. |
| Advisory session | A bounded technical question can be answered without taking delivery ownership. | Not suitable for an unresolved programme of work. |
How the work runs
Review the goal, current system, team, timing, location needs, and decision owner.
Use real workflows, code, data, constraints, and failure cases instead of a speculative feature list.
Write the output, responsibilities, assumptions, access, milestones, and handover.
Ship the agreed path, measure what changed, and make the next decision from evidence.
Relevant work
I helped launch 42 Lisboa and worked on the 42 Network student intranet. The wider archive includes full-stack products, AI publishing workflows, smart contracts, and Bitcoin infrastructure, with case-study evidence linked where it is public.
FAQ
I am based in Ericeira, in the Lisboa region. Remote work is the default; in-person planning in Portugal depends on the project, location, and timing.
Yes. I work remotely across Europe and plan explicit overlap for the team, release, and decision cadence.
English, French, and Portuguese. Project decisions and documentation use the language agreed for the team.
Yes. A focused AI opportunity or technical audit is often the responsible first step when the build boundary is still uncertain.
Remote delivery is the normal arrangement. A workshop or planning session in Portugal can be discussed when being in the room materially improves the work.
Send the product or workflow, what is currently stuck, the people involved, the important deadline, and the decision you need to make. A formal brief is not required.
Portugal-based · Europe-ready
I will tell you whether the responsible next step is an audit, a defined build, fractional direction, another specialist, or no project at all.
Discuss the work