LinnoEdge

LinnoEdge
Services

AI doesn't change companies.
Teams do. Processes do.
That's all we work on.

At a company I worked with closely last year, the head of IT walked me through their AI rollout — twelve tools, three vendors, a six-month timeline. Twelve months later, the tools were still running. The team had stopped using eight of them.

The gap wasn't the technology. It was that nobody had designed what happens after the demo.

"Nobody designed
what happens after the demo."
3
Countries
Japan · Vietnam · India
24
Month avg.
engagement length
End-to-end
Same team, from design
to maintenance
100
Dedicated team
model — no sharing
Why Three Core Services

Every AI rollout fails
at one of three points.

After working with companies across Japan, Vietnam, and India, I've seen the same failure patterns appear again and again. They're structural — and they're fixable if you know which one you're looking at.

01

The strategy exists. Nothing moves.

"We know we need to use AI. We've seen the demos. But nobody's figured out which decisions should stay with people and which ones we can actually automate."
Solved by
02

The plan is clear. There's nobody to build it.

"We've scoped out what we want. But hiring a dev team in Japan takes six months and costs more than we budgeted. And 'just find a vendor' has burned us before."
Solved by
03

The system is live. The team doesn't use it.

"Leadership is on board. The tool is deployed. But the middle layer — managers and frontline staff — hasn't changed how they work at all."
Solved by
↳ field observation Most companies come in at failure 1 or 2. Very few arrive knowing all three exist simultaneously — but when you ask carefully, they usually do.
What We Do

Five service areas.
One consistent team model.

Whether you're designing AI strategy, building systems, training staff, shipping mobile, or entering Vietnam — the same lab structure applies: dedicated teams, ongoing collaboration, no handoff at launch.

How It Works Together

Design. Build. Embed.
In that order — for a reason.

The three core services aren't separate offerings. They're sequential phases. Companies that try to skip phase one — or run all three at once — consistently hit the same wall: activity without adoption.

Phase 1
Design
AI Consulting
Define the boundary between what AI handles and what stays with people. Build a map of where automation creates value — and where it creates risk.
Starts with a 30-min session. No specs or proposals required to begin.
Phase 2
Build
Lab-model Development
A dedicated team — not a project crew — builds what the design phase defined. Same engineers from kickoff through to ongoing maintenance.
Monthly dedicated team model. Engineers stay on as the product evolves.
Phase 3
Embed
AI Training
The system is live. Now the organization needs to actually change. Layer-by-layer training ensures the tool becomes a habit — not a shelf item.
Four tracks: executive, management, mid-level, frontline. 60–120 min each.
↳ pattern observed Companies that run all three phases — even partially — consistently reach adoption faster than those that build first and train after. The design phase makes the training phase shorter. The training phase makes the tool actually stick.

How companies typically combine them

Case A — Most Common
AI Consulting → System Development: Start with a scoping session. Define what to build and what to automate. Then bring in a dedicated lab team to build it — without having to re-explain everything from scratch.
Case B — When the tool already exists
AI Consulting → AI Training: The system is deployed. The question is why people aren't using it. A brief diagnostic session, followed by targeted training at the layer where adoption is lowest.
Case C — Full transformation
AI Consulting → System Development → AI Training: Design, build, and embed in sequence. The most demanding path — and the one with the clearest outcome. Every layer sets up the next.
Start Here

Not sure which service to start with?
That's what the first session is for.

Every engagement starts the same way: a 30-minute conversation where I ask where things are stuck. By the end of it, we usually know exactly which of these makes sense first — and which ones to ignore entirely.

"Every engagement starts
the same way."
1
Book a free 30-minute session. No preparation needed. Just tell me where things are currently stuck.
2
We map your situation to the right starting point. Sometimes it's AI Consulting. Sometimes it's going straight to development. Sometimes neither.
3
If there's a fit, we scope next steps. If there isn't — I'll say so directly and point you somewhere that's a better match.
Shogo Harada, Linnoedge CEO
Who You'll Talk With
Shogo Harada
CEO, Linnoedge Inc. — Ho Chi Minh City

I've been based in Vietnam for 15 years. I run Linnoedge on AI tools — not as a pilot program, but as the actual operating model. Claude Code, daily. Structured prompting across every function.

The question I ask in every first session is the same: where are decisions getting made by instinct that could be made by data — and where is the opposite happening? That usually points to where to start.

Common Questions

Before you reach out

Answers to the questions that come up in almost every first conversation.

In a project model, there's a spec, a development phase, and a handoff. Once the product launches, the team dissolves. In the lab model, the same engineers stay on — handling maintenance, adapting to business changes, and building out what comes next. There's no knowledge gap at handoff because there's no handoff. This matters most six months after launch, when the business has moved and the system needs to follow.
No. Most clients arrive with a rough idea, not a spec. The first step is usually a scoping conversation — often after an AI Consulting session — where we define what to build, in what order, and what's genuinely unclear. Starting without specs is normal. Starting without a shared understanding of what you're solving is where problems begin.
AI Consulting, almost always. Not because it's a prerequisite — it isn't — but because the 30-minute session usually surfaces what the real question is. Sometimes a company arrives thinking they need development, and the conversation reveals the actual bottleneck is adoption. Sometimes the reverse. It's a cheap way to find out before committing to something larger.
Yes — and it's how most longer engagements work. Running AI Consulting alongside development is common: the consulting layer keeps asking whether we're still solving the right problem, while the lab team builds. Training works better after development is underway, once there's something concrete to train on. The combination depends on what phase you're in — the first session usually makes this clear.
AI Consulting: First session is free. Ongoing consulting varies by scope and frequency.

System Development / Mobile App: From ¥400,000 (~$2,600 USD) per engineer per month. Team size depends on scope.

AI Training: From ¥50,000 (~$330 USD) per session. Multi-session programs are scoped per company.

Vietnam Market Entry: Scoped by project — contact us for details.
For leadership tracks — yes, sometimes. Understanding what AI can and can't do well is genuinely useful before making decisions about where to invest. For frontline tracks, the training lands better when there's something concrete to train on. Telling people "AI will change your workflow" before they have a specific tool in front of them produces less behavioral change than training them on something they'll actually use tomorrow.
We're probably the right fit if you're looking for an ongoing partner — someone who stays with the product, asks whether the problem has changed, and adapts.

We're probably not the right fit if:
— You need a vendor to hand specs to and receive a finished product with no ongoing communication
— You need delivery in six weeks or less
— You need a team physically based in Japan
— You're primarily looking for the lowest-cost option

If any of those apply, I'll say so in the first conversation and point you somewhere that's a better match.