Code-defined
The product structure lives in code, not in undocumented GUI clicks or screenshots.
Small business operations / Agent-operable tools
I build small staff portals, reporting systems, trackers, dashboards, and internal admin tools that can be versioned, tested, deployed, and maintained by AI agents — delivered into your own environment.
小規模事業向けに、AIエージェントが保守できる社内専用プロダクトを作ります。
No customer-data custody. No GUI-only handover. No mystery setup.
Code-defined, Git-managed, testable, deployable internal tools that future AI agents can read, modify, verify, and hand over.
The product structure lives in code, not in undocumented GUI clicks or screenshots.
Changes can be reviewed, reverted, and handed over with real history.
Inputs, routes, forms, data rules, and critical workflows can be verified before deployment.
The system can be rebuilt and deployed from repeatable commands, not from memory.
Customer data and production infrastructure stay in your own Cloudflare, GitHub, SaaS, or Google environment.
README, schema, routes, tests, deployment notes, and prompts make future AI maintenance realistic.
Small internal products for owners, managers, and staff who need clearer records without giving up control of their data.
Procedures, checklists, reports, inventory notes, FAQs, manuals, and access-controlled staff pages.
Staff reports, photos, status, search, filtering, validation, and CSV export.
Opening, closing, cleaning, weekly tasks, completion history, and handover notes.
Lightweight stock memory before a full POS, accounting, or inventory platform is needed.
Internal intake, status, owner, follow-up date, notes, notifications, and export paths.
CRUD screens, filters, permissions, exports, API bridges, and index-maintainable handover.
Dummy-data examples of internal tools that can be read, tested, deployed, and maintained by agents.
Staff instructions, reports, and documents stop being scattered across messages, paper, and folders.
Built as a deployable internal product with dummy data, reusable content, and a structure an agent can inspect.
Incoming work gets an owner, status, follow-up date, and export path.
Designed for client-owned deployment and later migration into API-first SaaS or a custom internal product.
Client-owned delivery
I do not turn koichinishizuka.com into your customer database or business operating system.
Production belongs in your Cloudflare, GitHub, API-first SaaS, or Google account, with clear ownership.
Records should have CSV, JSON, API, or database paths that make migration possible.
The delivery includes enough structure for humans and future agents to maintain it.
Final pricing depends on scope, existing materials, data sensitivity, access requirements, deployment environment, and cleanup needed.
Small code fixes, workflow cleanup, existing internal tool review, or Airtasker-sized implementation tasks.
One small workflow such as a checklist, daily report, intake tracker, or inventory memo.
Staff-facing internal product with pages, forms, records, access control, and handover docs.
Database-backed internal tools deployed into your own Cloudflare and GitHub environment.
Process
Send the problem. Tell me what is messy, repeated, fragile, or too dependent on manual GUI work.
Choose the route. I identify what should stay no-build, what belongs in SaaS, and what needs an agent-operable internal tool.
Build and verify. I implement a code-defined version with tests, deployment notes, and dummy-safe examples.
Deploy and hand over. We move the tool into your environment with README, schema, routes, limitations, and next steps.
Origin Ministry bridge
For deeper diagnosis, Origin Ministry handles hidden losses, agent-readiness, and No-build / API-first SaaS / Agent-operable Tool / Client-owned Deployment decisions.