Architect & product builder · Forward-deployed

Turning complex needs into workable systems.

Ex-Accenture, Tencent, Deloitte.Architecture and product design, now built hands-on with AI agents.

Start a projectFollow the build

The model is never the answer.A workable system is.

  • Vibe-code the demo. Architect for production.
  • Most AI projects don’t fail on the model. They fail on architecture and process.

Twelve voices. One system.

An AI rollout in customer service: every stakeholder asks for something different. The work is turning that into one system that can ship.

Scenario: AI in customer service
What customers get
What the agents do
What keeps it safe
What it runs on
Same twelve needs, one workable system. Hover a block to see who asked for it.Illustrative

Now building with AI agents, hands-on.

Enterprise work taught me where systems break. Building with agents myself shows me where AI actually helps.

Follow the build log

Short takes and build logs on X. Longer write-ups on LinkedIn.

  • Co-founder

    Co-founding a startup

    I lead product planning and architecture, from zero to one.

  • Hands-on AI

    Agent workflows I build myself

    What I recommend to clients about AI comes from what I have built and used.

Four ways to start.

For consulting firms, tech teams and businesses. Each one starts as a single, clearly scoped piece of work.

If an AI workflow has to ship inside your team

Forward-deployed build

I join your team for a defined engagement, remote by default and on-site for kickoff and key workshops, to ship the first AI workflow.

Typical duration4–8 weeks

Typical outputs

  • A working AI workflow in your environment
  • Guardrails & handover docs
  • Roadmap for the next workflows
Start with this

If a brief or proposal needs a clearer argument

Solution design & communication

Structure the solution, explain the architecture, prepare material for client or leadership discussions.

Typical duration1–2 weeks

Typical outputs

  • Solution storyline & architecture
  • Solution deck / decision brief
  • Key assumptions & open questions
Start with this

If a new product or system change needs a workable scope

Product & architecture planning

Clarify capabilities, workflows, system boundaries and what to build first.

Typical duration2–4 weeks

Typical outputs

  • Product scope & capability map
  • System & integration architecture
  • Phased roadmap
Start with this

If an existing plan needs a second view

Independent solution review

Check requirements, dependencies and trade-offs. Flag what to resolve before the next step.

Typical duration3–5 working days

Typical outputs

  • Review findings & gaps
  • Technical options & trade-offs
  • Priorities for the next stage
Start with this

Durations are typical ranges, confirmed once the scope is clear. Implementation, ongoing maintenance and later phases are agreed separately when needed.

Have a complex need? Send the short version.

A useful brief covers four things. One clearly scoped task is a fine place to start.

  • The decision you need to make
  • Material you already have
  • The deliverable you expect
  • Your timing

Remote-first · Project-based · On-site when it matters

China · UTC+8

Not a project? Say hi:@helix_hoin/helixho