Your team is clearly AI-literate.
I'd be surprised if you weren't already testing several tools on real work.
That's why I want to spend the first fifteen minutes explaining why none of them — including ours — will solve the real problem.
A WORKSHOP WITH YAZAKI CORPORATION · 21 APRIL 2026 · BANGKOK
Yazaki
×
MonstarX
A two-hour working session on how your teams build enterprise software — and what the layer above the tool looks like.
presented by
WHAT CHANGED
Something shifted in the last two years — and accelerated in the last six to twelve months.
Non-developers can now build working software — in minutes, in their own language.
monstarx.com · EN
English
monstarx.com · JA
日本語
monstarx.com · TH
ภาษาไทย
11+
more languages
supported
supported
Fully localized — end to end. A quality inspector in Rayong doesn't need English to build something for herself. That is the difference between "anyone can build" being a slogan and being true.
WHAT AI ACTUALLY READS
Anatomy of a requirements.md.
Six essential sections. A basic one fits on two pages. A production-grade one runs fifty. The structure is the same.
01 – 06
the build order
the build order
01IDENTITY
Name. Audience. Voice.
"Budget planning for a Japanese-owned Thai subsidiary. Editorial, unhurried."
02STACK
Framework + the libraries that matter.
Next.js 15 · Tailwind v4 · Zustand
03DESIGN TOKENS
Colors, fonts, spacing.
--paper #FAFAF6 · Newsreader
04DATA MODEL
The nouns of the system.
Organization · BudgetVersion
05PAGES & FLOWS
Routes, and what each screen shows.
/variance/overview → op vs FX
06FORBIDDEN
Anti-patterns. What makes it wrong.
"No purple gradients. No emoji."
requirements.md
1,592 lines
The full YIC spec — what the demo app was built from.
Seven questions produce the brief. This produces the build order. MonstarX tooling bridges the two.
WHAT HAPPENS WHEN YOU DROP IT IN
Drop the brief. Get the build.
Drag your requirements.md into MonstarX. AI expands it into a structured build brief — ready for the engineers, human or agent.
INPUT → OUTPUT
minutes, not weeks
minutes, not weeks
.md
requirements.md
your one-page brief
→
mX
MonstarX AI
expands, structures, validates
→
A structured build brief
six sections, ready to hand off
01OVERVIEW
02TECH STACK
03CORE FEATURES
04PAGES
05VISUAL DESIGN
06KEY DECISIONS
THEN IT JUST… BUILDS.
A phase-by-phase build plan. Executed in the browser.
MonstarX turns the structured brief into a sequenced build plan — pages, flows, data, integrations — and runs it live. No IDE. No local setup. No terminal.
LIVE IN BROWSER
zero technical knowledge
zero technical knowledge
monstarx.com/build · YIC Budget Planning System
51 / 76 tasks
×
NO IDE
×
NO CODING
×
NO ENVIRONMENT SETUP
ZERO TECHNICAL KNOWLEDGE
WHAT IF THE REQUIREMENT ISN'T WRITTEN DOWN?
No brief. Only code.
Every enterprise has one — a system that still runs the business, but no one can tell you what it does, how it works, or what it would take to change. The docs are gone. The vendor moved on. The person who built it left three years ago. All that remains is the code.
THE INHERITED CODEBASE
a map, not a rewrite
a map, not a rewrite
"What does it actually do?"
Nobody here remembers.
Nobody here remembers.
"What's the security posture?"
Nobody knows.
Nobody knows.
"What would it take to modernize?"
Nobody can tell you.
Nobody can tell you.
OUR ANSWER
moncode.ai
from the MonstarX teamDrop the repo. Get the map.
One zip file — or a public GitHub URL — in. Out: a knowledge graph of every file and function, an auto-generated PRD, a security audit, and an AI agent that actually knows the code.
KNOWLEDGE GRAPH
AUTO PRD
SECURITY AUDIT
SEQUENCE DIAGRAMS
AI CHAT (grounded)
100% local. The proprietary code never leaves the laptop. No uploads. No cloud processing. BYO key (OpenAI, Anthropic, Gemini, Ollama).
KNOWLEDGE GRAPH
AUTO-GENERATED PRD
SECURITY AUDIT
AI CHAT · GROUNDED
"Six tools. One repo. Zero onboarding."
moncode.ai — MonstarX, for code you didn't write.
WHAT WE'LL SHOW YOU NEXT
Three demos, three starting points.
Each one begins where most enterprise engagements actually begin — with a different kind of mess. From no documentation, to a brief no one trusts, to a finished system that still needs to be understood.
THE MENU
pick any. or all three.
pick any. or all three.
I.
DEMO ONE
No brief.
Only code.
We reverse-engineer your existing system into a brief — a knowledge graph, an auto-PRD, and an AI agent that knows the code.
LIVE AT
moncode.ai
the inherited codebase
II.
DEMO TWO
From brief
to POC.
Drop your requirements. Watch MonstarX structure, expand, and build — live in the browser. No IDE. No setup.
LIVE AT
monstarx.com
a working proof, in minutes
III.
DEMO THREE
One we
prepared earlier.
A production-quality budget planning application — built this week, ready to walk through. The destination, not the journey.
LIVE AT
yazaki.monstarx.com
the cooking-show moment
WHAT THIS IS
An end-to-end budget planning tool — with the accounting rule that matters.
Plan, submit, approve, consolidate, and analyze — designed for a Japanese-owned Thai subsidiary. THB spend, JPY reporting, an FY that runs April to March. Variance broken into operational and FX so the Thai team's work is separable from treasury noise.
localhost:3000/dashboard
THE DASHBOARD
Dense without clutter.
The opening screen is lived-in. No empty states, no "Welcome back." Five bands of information dense enough for a CFO and legible enough for a GM who prefers paper.
- A Fiscal context strip
- B Three hero metrics — Display XL Newsreader
- C Six department cards with YTD + variance
- D 6×12 variance heatmap + live activity feed
- E Alerts needing attention
localhost:3000/dashboard
BUDGET ENTRY · WOW 5 + WOW 6
A spreadsheet, inside an enterprise tool.
11 cost categories × 12 months. Type =LASTYEAR*1.1 or =SPLIT(180M/12) in any cell. Every cell shows the prior-year actual as a ghost number — finance staff live in spreadsheets; give them spreadsheet muscle memory inside an enterprise tool.
- · Tab / Enter navigate · = starts formula
- · Right-click any cell for quick actions
- · Ghost values update if prior year changes
/budgets/BV-D-MFG-HAR-FY2026-PLAN/edit
APPROVALS
The chain of sign-off, visualized.
Five steps by default; six when the budget crosses THB 50M (HQ reviewer appended). The current step glows ochre. Every action is a comment, every comment becomes an audit entry.
- Approve · routes to the next step
- Return for revisions · sends back with a required reason
- Reject · stops the chain
/approvals/AR-MFG-HAR
WOW 7 · THE AUDIT TRAIL AS A TIMELINE
Not a log.
A story.
The audit trail renders as an editorial timeline — time labels in a rail, an avatar, a sentence written like an editor wrote it. Quotes render in Newsreader italic with an ochre rule. The microcopy is the feature.
"Saegusa Shoji returned v2, asking the team to revisit Q3 headcount assumptions — the labor line read as optimistic against plant capacity."
/approvals/AR-MFG-HAR/audit
WOW 2 · VARIANCE OVERVIEW
The money shot.
A horizontal stacked bar splits the plant's variance into Operational and FX. One glance answers the question every Japanese GM asks: did the Thai team overspend, or did the yen weaken?
Toggle Exclude FX and the bar becomes 100% operational. Thai team's execution shows cleanly without treasury noise.
/variance/overview
WOW 1 · THE CASCADE
Change one number. Every number updates.
Open /admin/fx-rates, set the Actual rate from 4.02 to 4.15, flip to Variance Overview. Every JPY figure slot-rolls to its new value. Operational variance is unchanged — rate movement is treasury's problem, not operations'.
LIVE IN THE DEMO
Try 4.15 yourself — or run the cascade from /admin/fx-rates.
/admin/fx-rates
FX IMPACT ANALYSIS
Treasury-level signals, isolated.
The FX rate timeline shows plan (dashed), forecast (stepped), and actual (solid). A sensitivity table quantifies how each department moves per ¥1 weakening of THB — so a hedging conversation starts from concrete numbers.
/variance/fx-impact
AI NARRATIVE
Not magic. An augmentation layer.
Variance metadata feeds an LLM that drafts commentary in the voice of a finance controller. The operational/FX split is deterministic; the prose is the augmentation. Analyst can accept, edit, or dismiss.
"Harness Assembly exceeded plan by ¥5.77M in June. ¥3.08M (53%) is operational — driven by a 6% copper price spike. The remaining ¥2.69M (47%) is FX."
/variance/narrative
REPORTS
Five standing reports, plus a real pivot builder.
Dept P&L vs Plan · HQ FY Summary (Japanese taxonomy, JPY-first) · Variance by Category · FX Impact · Approval Status. Every number lives — change the FX rate and re-run; the numbers track.
/reports/library
REPORT BUILDER
A real pivot.
Not a mockup.
Three dimensions (department, category, period), seven measures, dept-level filters. Row-dim + optional column-dim + any number of measure columns, totals in both axes, live preview.
Click Save as preset and (in production) it lands in the library.
/reports/build
DISCOVERY PROMPT · INTEGRATIONS
Where your systems plug in.
We haven't yet confirmed Yazaki's today-state. This page sketches the connectors we'd wire so the conversation can start from concrete mockups, not an empty square. Every row is labeled Not connected until we hear otherwise.
SAP S/4HANA · Oracle E-Business Suite · Dynamics 365
Workday HCM · Xero · Bloomberg FX (connected mock)
Slack · Teams · Power BI
/admin/integrations
PERSONA · PHONGSAK (DEPT MANAGER · IT/BMS)
His own budget and three approvals waiting.
Phongsak's D-IT-BMS plan is still a draft — the MonstarX accelerator-tier license is flagged on line 56000, visible from the dashboard's activity feed. His approval inbox has three peer-dept reviews. He sees his own name in audit trails and comments.
- · Edits D-IT-BMS plan
- · Reviews 3 peer approvals routed to him
- · Notifications: 3 unread at login
/approvals/inbox
PERSONA · SAEGUSA SHOJI (GM · 工場長)
The plant view.
Saegusa-san opens the dashboard and sees the full plant: ¥1.43B annual plan, YTD variance split at a glance, six departments. His signature is on D-FIN and D-HR approvals. When budgets cross THB 50M, the chain tells him HQ review is coming next.
- · Variance Overview is the daily read
- · Include/Exclude FX toggle separates signal from noise
- · Returns budgets with notes that land as prose in the timeline
/variance/overview
PERSONA · SUWATCHAI APIWATANA (FINANCE)
Owns the rates. Publishes the reports.
Suwatchai sets the plan rate in February, updates the forecast at Q1, and monitors the Bloomberg feed for the actual. Every report is on her desk — the HQ FY Summary in Japanese taxonomy ships from here.
- · FX rates, rate audit log
- · Runs all 5 standing reports
- · Builds ad-hoc pivots for management
/admin/fx-rates
PERSONA · TANAKA HIROSHI (HQ REVIEWER · 本社)
Only sees budgets above threshold.
Tanaka-san sits in Tokyo. He appears in the approval chain only when a plant budget crosses THB 50M. His view emphasizes JPY, the HQ taxonomy, and cross-subsidiary consolidation.
- · HQ FY Summary is his primary document
- · Reviews D-MFG-HAR (180M) and D-ENG (62M) this cycle
- · No rate setting, no line edits — review-only
/reports/R-HQ-FY/preview
WOW 3 + WOW 4
Mouse is optional.
Press ⌘K from anywhere to jump to any page, any department, any budget. Press ? for the full shortcut legend. It reads like Linear or Superhuman, not like an ERP.
- · Command palette groups: Recent · Navigate · Departments · Budgets · Actions
- · G-prefix mnemonics (G then D/B/A/V/R) for the power users
/dashboard
⌘K opens anywhere — even inside inputs.
DARK VARIANT
Warm paper or warm paper at night.
Full dual-token palette under [data-theme='dark']. Never pure black — a warm near-black surface that reads like night-mode print. Every semantic color remapped for contrast.
/dashboard · dark
A TOUR OF THE PRODUCT
What we've been building, briefly.
A product vision deck — one operating system for the full innovation pipeline, from signal to shipped. Six stages, one unified system.
THE DAILY LAYER · AND THE SIGNAL IN
Where your people live — and where the pain arrives.
FROM IDEA · TO PROTOTYPE
Validated pain becomes working software.
VALIDATE · AND INSTITUTIONALIZE
Real users. Real evidence. Never lost.
CLOSE
Let's build
what's next — together.
What you saw was built in days. Imagine what we can ship in a quarter, alongside your team — the July budget system, production-ready. Pick the first sprint. We start when you do.