Creative & ecommerce
Turn product inputs into a usable creative brief.
Carry approved facts and brand rules into the next design task, with an explicit reviewer and destination.
- Sample handover
- A source-linked brief and review checklist
Independent FDE engineer · Enterprise AI
Make your AI tools
work together.
Turn repeated handoffs into a workflow your team can run. I connect your existing tools through Codex, capture company know-how as Skills, and work alongside your people from first assessment to handover.
Work directly with Leon, an independent Forward Deployed Engineer. Start with one business process, a named owner and clear acceptance checks.
- Remote delivery
- English communication
- Europe & North America
For ecommerce & creative teams
Your team has AI tools. You want a business process that works across them. Start with one recurring product-content task, connect the required systems, and capture the procedure so your team can use it.
A delivered workflow change
Connected tools.
Reusable company workflows.
An anonymized enterprise project brought design SaaS and office workflows together through Codex. Company-specific Skills captured procedures for reuse across the connected work.
Anonymized delivered project
From specialist tools
From specialist tools
to a shared way of working.
Image production began in specialist AI design SaaS. The project introduced Codex as a shared entry point for connected design and office workflows.
Company-specific Skills captured repeatable procedures, while connections carried information between business platforms.
Read the public project account ↗Design SaaSOffice systems
Shared work entry pointCodexConnected workflows and business data
Company-specific SkillsReusable procedures for the connected work
Shared with permission as a project-level workflow overview. Read the case overview ↗
Explore the possibilities
See the work.
Picture it in your team.
Four interactive examples show the inputs, decisions and handover a workflow needs. Open a sample, then see what happens when an essential input is missing.
Illustrative workflows with synthetic data and simulated outputs. These are demonstration scenarios, not additional client projects.
Team knowledge
Make answers traceable to the source.
Build a reviewable answer from approved documents, and show where a question needs a person to resolve it.
- Sample handover
- An answer, source register and open questions
Project delivery
Give meeting decisions a clear next step.
Separate decisions from suggestions, propose accountable actions, and check them before updating a task system.
- Sample handover
- A decision log and owner-reviewed action list
Business operations
Bring the exceptions to the right person.
Compare records with agreed rules, preserve the supporting evidence, and propose a next step for review.
- Sample handover
- An exception queue with evidence and owners
Want to try a longer sequence? The image workflow demo includes review, revision and a failed handoff.
Try the image workflow demo ↗01 / A practical path
One workflow.
A clear next step.
FDE means working closely with the people doing the work and taking part in the implementation. Each stage gives you evidence for the next investment decision.
A focused paid assessment
One workflow, up to two systems and five representative examples. A working session and decision call turn the bottleneck into a clear implementation decision.
You leave withA workflow map, evidence sheet, feasibility note and build / adjust / stop recommendation.
Build & evaluate a pilot
Start with one workflow, up to two named connections, one environment and five pilot users. Build a company Skill where appropriate, with human review, failure handling and agreed evaluation.
You leave withA working pilot and evidence to stop, improve or expand.
Implement & enable
Work alongside designated staff on the next priorities. Document the process, review real usage, and help your team run and improve the system.
You leave withAn agreed implementation, operating guidance and a handover.
The assessment stands on its own; a pilot is optional. Fees, dates, system operations and acceptance checks are agreed in writing before paid work begins. Read the assessment scope.
A decision you can use
See what the first
engagement leaves behind.
Before commissioning a build, know which handoff to improve, what access it needs and how your team will judge the result. The assessment gives you a practical decision document.
Explore the four assessment deliverables ↗ILLUSTRATIVE ASSESSMENT EXCERPT01 / WORKFLOW BOUNDARY
From reviewed image to recorded result.
- Current friction
- People copy accepted files and update a task by hand. A failed update leaves the next person unsure what is ready.
- First boundary
- One asset library and one task system. A named reviewer selects the accepted version.
- Acceptance check
- The accepted file and its task link agree. A failed sync can be retried without recreating the image.
- Evidence to collect
- Manual handling time, missing links and recovery effort. Measure before and during the pilot.
02 / Built for your team
The work should
have an owner.
And a way forward.
A useful implementation includes the people, instructions and checks needed to keep it running. The engagement is designed around an agreed handover.
Deliverables, ownership and third-party license terms are specified in the engagement agreement.
A reusable company Skill
Agreed instructions, references and supporting scripts, with inputs, outputs and an owner.
An implementation in the agreed environment
System connections, access permissions, review points and exception handling.
A way to measure what changed
A baseline and agreed checks for quality, human effort, adoption and running cost.
People prepared to take over
Operating instructions, practical training and a handover exercise for designated staff.
04 / Open to inspection
Public engineering work.
Independent open-source contributions offer a concrete look at my engineering work. Each link opens the problem, proposed change and public review.
MCP Context ForgeMerged · 2 Oct 2026
Keep tool catalogs intact after reconnecting.
Preserve gateway catalog data when OAuth discovery returns an empty result.
AI-Infra-GuardMerged · 3 Oct 2026
Make security reports usable by downstream tools.
Retain remediation guidance in valid machine-readable SARIF reports.
FlowGramMerged · 29 Sep 2026
Save the workflow users actually edited.
Correct workflow serialization after a node moves.
These are independent contributions, not client engagements or organizational endorsements. AI-assisted tools are part of the development workflow.
Before we begin
Practical questions.
Clear expectations.
Is this right for our team?
A useful starting point is a recurring process, a named owner and two tools between which work gets stuck. Ecommerce operations and creative teams are an initial focus. Bring a few representative examples; we can establish whether there is a focused assessment to do.
Do we have to change our existing tools?
We assess the tools you already use and their permitted integrations. Codex and company-specific Skills can coordinate suitable work, but each connection depends on actual access and capabilities. The assessment identifies what can be connected and what needs a manual step or further validation.
What access do you need to start?
Begin with a general description and redacted examples or a screen-share. For implementation, we agree the environment, allowed data and precise read/write operations before granting access. Send no passwords or confidential files through this website.
What does it cost, and what happens after the assessment?
The assessment is a paid, separately scoped engagement. Its fee and delivery window are confirmed in writing before work begins. You receive the findings whether or not you choose a pilot. Any implementation and third-party software costs are quoted separately for the agreed scope.
Who will do the work and help our team take over?
You work directly with Leon, an independent FDE engineer (Forward Deployed Engineer). A pilot includes the agreed implementation, operating guidance and a handover exercise for your designated owner. Deliverable ownership and third-party licenses are specified in the engagement terms.
Are the workflow examples real client projects?
The four interactive examples use synthetic data to show how I would structure an assessment and pilot. The separately labelled delivered project is an anonymized, permissioned account of connecting design and office workflows through Codex. Public GitHub contributions are engineering evidence; they are not client endorsements.
How do we work across time zones?
Delivery and written communication are in English. I work from China during China business hours. We agree meeting overlap before starting; European mornings often overlap, while North American collaboration can begin asynchronously. A specific meeting time is confirmed for each engagement.
Start with the business problem
Which workflow
would you change first?
Start with a short English fit discussion. Describe one recurring task and its two main tools; we can decide whether a paid assessment is useful.
Email Leon[email protected]
- Share one process.Tell me where work gets stuck and which two tools are involved.
- Check whether it fits.We clarify the owner, examples and next decision, by email or an agreed call.
- Agree a written scope.You review the deliverables, fee and dates before any paid work starts.