We build mobile apps, AI automation, POS and payment systems, and web platforms for small and medium businesses — retail chains, manufacturers, accounting firms, transport operators, property agencies. We design the architecture, build it, and keep operating it after launch. You own the code and the accounts from day one.
Six service lines, all of them things we have shipped into daily commercial use rather than things we are willing to try. If your project sits across two or three of them — which most real business systems do — that is normal; the architecture conversation covers the whole thing at once.
Native iPhone and iPad apps for field teams, sales floors, and customers — built in Swift, submitted to the App Store under your own developer account.
Android apps and on-device software for staff, drivers, and counters — including hardware-attached builds on scanners, printers, and payment terminals.
React Native and Flutter apps that ship to both stores from a single codebase, when the app is business logic rather than heavy device work.
AI agents, document pipelines, and LLM features that remove a named piece of manual work — with a human approval step and an audit trail.
Point of sale, RFID/NFC cards, payment terminals, and cloud sync for multi-branch retail, food service, and transport operators.
Internal platforms, customer portals, dashboards, and marketplaces — the system your business runs on, not a brochure website.
We do not sell hours and we do not send a proposal before we understand the problem. Four steps, and you can stop after any of them.
You describe the business problem — the manual process, the spreadsheet that broke, the app your customers keep asking for. We ask about volumes, branches, staff, and what happens today when something goes wrong. No obligation, no deck.
Before anyone writes code you get a short document: what the system is made of, which parts are risky, what we build first, and what we deliberately leave out of version one. This is where most of the money is saved or lost.
You get something you can open and click every one to two weeks, deployed to a real environment. Fixed-scope phases rather than an open-ended hourly meter, so the budget is knowable before we start each phase.
Store submission, staff training, monitoring, and a support arrangement. We stay responsible for uptime and for the platform updates that arrive every year whether you planned for them or not.
Most businesses that come to us have been burned once already. The pattern is always the same: a cheap development shop quoted a low hourly rate, delivered something that demoed well, and then the business grew — a second branch, a second country, a tax change, a payment provider switch — and the change turned out to be impossible without a rewrite. The build was cheap; the second build was not.
That happens because nobody designed the system, they only wrote the features. We start with the boring decisions that are expensive to reverse: how data is separated between branches or tenants, what happens when the network drops, how money movements are recorded so they can be audited later, and which third-party services you can walk away from without a rebuild. Those decisions cost a week of thinking at the start and save quarters of work later.
The second half of the argument is operational. We run our own products in production — an AI accounting workflow platform used by Japanese tax firms, a 3D AI agent workspace, and an executive dashboard and simulator — so we carry the cost of our own architectural shortcuts. That is a different incentive from a shop that invoices the hours and moves on. You can read what that looks like in practice in our case studies, or on the about page.
A 30-minute call with an engineer, in English or Japanese. You will get an honest answer on scope, timeline, and whether we are the right fit — including when we are not.