Marketing,sales,service,technology.One engine.

I've spent 18 years connecting them into one system. Now I'm building hireEnna, the AI school that teaches founders to design their own revenue engine.

Alex ChiangRevenue engineer, Taipei and Los Angeles

The framework

A revenue engine has four layers. The order is the method.

Every framework I learned from teaches a piece: inbound, launches, funnels, value ladders. Almost all of them are marketing, and none of them connect to sales, service, or the technology that holds it together. Revenue engineering connects them.

Layer 1

Foundation

What is true about this business?Without it, everything downstream is generic.

Layer 2

Infrastructure

What connects, stores, and remembers?Without it, every channel keeps its own truth.

Layer 3

Demand

How does a stranger become a buyer?Without it, spend goes up and nobody can name the leak.

Layer 4

Operation

Who runs it, and how does it get better?Without it, the system gets built once and decays.

There are three kinds of work on an engine. Build is commoditized. Operate is what agencies do against a design they didn't create. Design is the part almost nobody can do, which is why I'm trying to make it learnable.

1M+

Downloads of Sword Quest, with 300,000 monthly players at its peak.

$5M

A consulting firm I helped grow from $500K, reaching $3M within two years.

$600K

A year for an Apple accessories startup that started from zero, on a self-liquidating funnel.

2×

Both engines returned better than $2 for every $1 spent on paid acquisition.

Alex Chiang

Where it started

I set out to build a game. I learned to build engines.

In 2008, at 26, I co-founded Doremi Star in Taipei with my savings and $1M from my family. Our Facebook game, Sword Quest, put players behind the counter of a blacksmith's shop: forge a sword with your friends, pull the cloth off, see what you made. Seven of us built all of it: the art, the game design, the economy, the servers and the marketing.

I was the one reading the numbers every day: who installed, who came back, who paid, who quit at which level. That is where I learned that a product doesn't grow because it is good. It grows because somebody designed the system that turns attention into revenue.

2008

Doremi Star founded in Taipei.

2011

Sword Quest goes live on Facebook, later in four languages.

2013

AppWorks Accelerator, Batch 7. Over a million downloads.

2015

After seven years, I shut it down.

The Sword Quest workshop, with a sword being forged on the table
The workshop. Friends hammer your sword and both of you get better at the craft.
A gold-framed card revealing a new flame sword
The uncover. The moment both 2012 reviews named as the best in the game.
A battle against a zombie with a small puzzle board
Adventure mode. The swords you made finally had a job.

The product worked. The economics didn't. That failure is why I spent the next decade on revenue systems.

Built along the way

Every one of these was a revenue engine I had to design.

A page from the Inbound Marketing manga: the consultant explains awareness, consideration and decision
Inbound Marketing, the manga. Three chapters made with my team as agency marketing. Read it

Gogo Partners

The first HubSpot Solutions Partner in Taiwan. Revenue architecture and full HubSpot builds for listed tech companies, across 50+ industries.

Inbound Taiwan 2019

A 300-person paid event with speakers from HubSpot and Google, fully covered by ticket sales.

Inbound Marketing Mastery

100+ hours across 12 modules at $2,000 a seat. More than 50 seats and $100K in revenue. See the course

Taiwan's first self-liquidating funnel

ClickFunnels mechanics rebuilt on WordPress with local payment gateways, since Stripe isn't available here. About $22K before the market saturated.

DoubleCRM

A white-labeled GoHighLevel for Taiwan, with a UI translation layer my team coded, Taiwan payments and LINE.

What I'm building

What if a founder could design their own revenue engine?

hireEnna is an AI school for revenue engineering. Enna teaches, designs and reviews. The founder builds their Revenue Brain and runs the engine in the tools they already use.

The school live

Enna teaches the framework one question at a time and turns the answers into files. Those files are the Revenue Brain, the one asset that compounds.

Design and review live

Enna designs the engine and reviews the result. Execution happens in Lovable, HubSpot or GoHighLevel, through briefs and connections.

Multiplayer next

Marketing, sales, service and the owner building one shared brain, instead of a thousand private AI threads.

Follow the build.

I write about revenue engineering as I build the school for it. If you'd rather talk about your own revenue system, the architecture conversation is open.