Eitoss
From an Idea to a Funded Product in 12 Weeks
Eitoss came to us with a vision for better workplace communication. We shipped a demoable MVP in 8 weeks and had the product live in 3 months. They raised 60 million yen in funding. Two years later, we're still building together.
How It Started
Eitoss had a clear problem to solve: frontline workers and management weren't communicating well. Important feedback got lost. Good ideas never reached the people who could act on them. The gap between the factory floor and the leadership team was costing real money and real morale.
They came to us with a vision rooted in Kaizen -- the Japanese philosophy of continuous improvement. The idea was simple: give every worker a voice, and give management the tools to actually listen.
This was personal for us too. Eitoss was one of AcornGlobus's first projects -- the engagement that helped spark the company. We didn't treat it like a client brief. We treated it like building something of our own.
What We Built Together
We didn't just write code to a spec. We worked with the Eitoss team to shape the product -- questioning assumptions, trimming scope to what mattered most, and making sure every feature earned its place in the MVP.
Kaizen Communication Channels
Structured feedback channels that let frontline workers submit improvement ideas, report issues, and communicate directly with management. Every suggestion gets tracked and routed to the right person.
- Organized feedback with priority routing
- Improvement suggestion tracking
- Action item management so nothing gets lost
- Clear accountability for every submission
AI-Powered Knowledge Base
Workers ask questions in plain language and get instant answers, powered by Gemini and ChatGPT APIs. The system learns from interactions and gets smarter over time.
- Dual AI integration for better responses
- Contextual answers based on company knowledge
- Handles queries in natural language
- Learns from every interaction
Analytics That Actually Help
A dashboard that shows managers what's working and what isn't -- response times, engagement rates, improvement trends. Not vanity metrics. Actionable insights that help teams get better.
- Response time tracking
- Engagement and adoption metrics
- Improvement trend reports
- Team-level and org-level views
The 12-Week Journey
From first conversation to a funded product.
Discovery (Week 1-2)
We spent two weeks understanding the problem deeply -- talking to stakeholders, mapping out user flows, and scoping the MVP to what would actually prove the concept. We cut three features that sounded important but weren't essential for validation.
Design (Week 3-4)
UI/UX design focused on simplicity. The platform needed to be usable by frontline workers who might not be tech-savvy. We prototyped, tested, and iterated until the flows felt effortless.
Build (Week 5-10)
Six weeks of focused development. Sprint demos every two weeks so the Eitoss team could see progress, give feedback, and course-correct in real time. By week 8, we had a demoable product.
Launch (Week 11-12)
Testing, deployment, and onboarding real users. The product went live. Early adopters started using it. The data started coming in.
Technology Stack
We chose each technology for a reason -- scalability, developer velocity, and long-term maintainability.
What Happened Next
The MVP was just the beginning.
Raised 60 Million Yen
Eitoss used the working product to raise funding. Investors could see real users, real data, and a real product -- not a slide deck.
Early Adopters Validated the Concept
Real companies started using the platform. The feedback loop we'd built into the product proved its value from day one.
We Kept Building Together
After funding, Eitoss didn't go hire a new team. They stayed with us. Two years later, we're still growing the product together -- not because of a contract, but because the partnership works.
The Product Keeps Growing
New features, new integrations, expanding to new industries. The code we wrote in those first 12 weeks was built to last -- and it has.