Skip to main content

Linnoedge

Linnoedge

Works — Software Development Case Studies

What the spec never captured.

Five real projects across five industries — a KGI monitoring dashboard, a data SaaS for 3,200+ machines, an enterprise migration off Salesforce, a 14,284-member executive SNS built in Flutter, and a search and consultation platform for licensed professionals. The honest account.

// Linnoedge — Projects as of 2026.05
5 case studies published. Pharma patient system: released 2026.02.28.
BizOn! SNS: iOS/Android/Web released. Data SaaS: active deployment.

3hrs → 0

daily manual tallying
fully automated

← Pachislo SaaS

200+

migration bugs resolved
one by one

← Pachislo SaaS

32pd

to build the KGI dashboard,
after scope was clarified

← Telemarketing SaaS

Every project had a moment where the spec wasn't enough.

Undocumented workflows running in production. A mid-project handover nobody planned for. A four-company chain where every decision had to clear three approval layers.

That's when the real work started. This is that work.

Case Studies

Software Development — 5 Projects from the Field

10 project pages published in total. The five above are full case studies — development process, decisions, and outcomes. The rest are project summaries.

The numbers existed. Nobody could see them.

0.19s

Over the SLA threshold.
The gap between "running" and "usable."

32 person-days. Requirements and development running in parallel across a four-company chain. SQL response hit 2.69 seconds — above the 2.5s SLA. Index restructuring, query splitting, cache redesign. That last 0.19 seconds was the actual project.

"No cross-tab analysis — just deliver these KGIs for this quarter." Scoping down once kept the team's priorities clear every sprint after that.

What we fixed
Call records aggregated by hand in Excel
KGI dashboard (SQL tuned to the 2.5s SLA)
Each rep and campaign's progress is visible

"Because we scoped it down, everyone always knew what mattered." — client lead

  • Next.js
  • TypeScript
  • PostgreSQL
Read the case
Every morning, three hours of someone's day disappeared.

3,200+

machines auto-synced daily.
Was 3 hours of manual work.

Day one code review made it clear: this wasn't built for production scale. The previous vendor had left mid-project. We weren't inheriting a codebase — we were starting over.

Four months. Separate feature sets designed for three distinct user types: hall operators, data creators, and end users. 200+ bugs surfaced during migration. We resolved each one. "Cutting corners now becomes maintenance cost in three years" — that was the call.

What we fixed
3 hours of manual data entry every morning
A pipeline that auto-syncs 3,200+ machines daily
Data reaches hall operators, data creators and end users

"We built a habit of looking at the numbers. That mattered more than the 3 hours." — CEO

  • Laravel
  • Docker
  • Stripe
Read the case
The workflow that ran the operation wasn't in the spec.

4mo

Full rebuild. 5 years of patient
data migrated. Shipped.

Three weeks into requirements, a fax confirmation flow came up for the first time. Not a single line in the official spec — but it ran every day in production. "Everyone knows it, so nobody wrote it down." That sentence kept coming back.

Full rebuild in React.js + Nest.js. Five years of patient records off Salesforce. Four functions built in-house: fax send/receive, CSV automation, document output, and physician sync. Four months, live February 2026.

What we fixed
Salesforce, plus a fax confirmation flow not in the spec
Full rebuild in React.js + Nest.js
Fax confirmation and CSV automation run inside one system

"The parts we'd bent to fit Salesforce finally became visible. When the fax flow appeared on screen, that was the moment." — client IT lead

  • React.js
  • Nest.js
  • FAX API
Read the case
Executives were connecting. The platform that sustained them wasn't.

14,284+

executives active in 30 days.
One of Japan's largest executive networks.

BizOn! has the full feature surface of a modern social network — feed, DMs, matching, events, push notifications — built in Flutter. One Dart codebase, three platforms, 14,284 active executives in the first 30 days. One of Japan's largest executive networking communities.

Adding an ad placement revenue layer triggered three simultaneous constraints: Apple's Steering regulation (pricing data in a Dart bundle becomes part of the iOS binary), GMO's redirect-based 3DS authentication, and Japan's Special Commercial Transactions Law. All three, on a live platform, coordinating iOS App Store, Google Play, and web in a single release window.

What we fixed
Membership fees were the only revenue
Ad platform (pricing and payment stay on the Web)
Companies apply and pay on the Web; ads run in the app

"The ad platform launched without a single support ticket about billing. The payment flow just worked." — CEO, WizBiz

  • Flutter
  • iOS · Android · Web
  • GMO Payment
Read the case
The professionals were there. People just couldn't find them.

30+ screens

Users, professionals, admin —
scattered needs, one platform.

End-to-end build — requirements to delivery — of a two-sided platform: region search, public Q&A, real-time chat, reviews, and an article CMS, across 30+ screens and an admin console.

Phase 1 was deliberately scoped: prove the core loop — find, ask, consult — before layering on scheduled paid consultations and the rest.

What we fixed
Word of mouth, thin directories, a cold phone call
Region search, public Q&A, chat, reviews and articles in one place
Find, ask and consult become one path
  • PHP
  • Laravel
  • MySQL
Read the case

More projects

LingaLink
AI / EdTech / Social Learning
→
EduMate
AI / EdTech / Collaborative Learning
→
OfficeBrain
AI / RAG System
→
AiGen-One — Enterprise LLM Platform
Enterprise AI / RAG / Governance
→
T-Shirt Design Simulator
Web
→

From the field — the Linnoedge team

Why teams come to us

Some projects we almost turned down. Too many stakeholders. Requirements still being defined mid-sprint. A previous vendor that left halfway through.

But that complexity is exactly where we've learned to be useful.
When the spec doesn't cover the real operation — that's our kind of problem.

If you're hesitating to reach out because the situation feels too complicated — that's actually a reason to call, not to wait.

If that sounds familiar, let's talk.

— The Linnoedge team

Frequently asked questions

What industries does Linnoedge work in?

We've delivered in pharma, regulated gaming data, and B2B SaaS — but the industry isn't the common thread. It's projects where undocumented workflows are running in production and the spec alone isn't enough. Our team is based in Vietnam with Japan-facing project management, which means we bring both cost efficiency and operational familiarity with Japanese business processes.

How long does a typical project take?

The five cases on this page each ran 3–4 months from kickoff to delivery. When requirements aren't finalized, we start with scope clarification rather than setting a deadline first. "When to start" matters less than "what we're actually building" — and getting that right early saves time later.

Can you take over a project that a previous vendor abandoned?

Yes. The regulated gaming data platform was exactly that situation — the previous vendor left mid-project and we inherited an unfinished codebase. We run a structured code review on day one and give an honest assessment: rebuild or continue from here. Complex handovers are where we tend to be most useful.

Contact

Let's talk through it.

30 minutes is usually enough to figure out what's actually needed.

Who this is for Teams that have had a difficult vendor experience and want to do it differently next time.
Requirements don't need to be finalized. Pre-vendor-selection conversations are fine.
Book a 30-min consultationContact us