Code-defined
The product structure lives in code, not in undocumented GUI clicks or screenshots.
Small business operations / CLI-operable tools
I build small staff portals, reporting systems, trackers, dashboards, and internal admin tools that AI agents can create, change, test, and deploy through CLI/API workflows — delivered into your own environment.
小規模事業向けに、AIエージェントが保守できる社内専用プロダクトを作ります。
If an agent cannot build and maintain it through CLI/API, I do not sell it as a core product.
Every core tool must be code-defined, Git-managed, command-driven, testable, deployable, and reproducible by an AI agent.
The product structure lives in code, not in undocumented GUI clicks or screenshots.
Scaffolding, migrations, tests, build, deploy, and routine updates run from documented commands.
External platforms are acceptable only when the needed configuration and data paths are scriptable or API-driven.
Inputs, routes, forms, data rules, and critical workflows are verified before deployment.
Customer data and production infrastructure stay in your own Cloudflare, GitHub, or API-first platform environment.
Google Sites, AppSheet, and GUI-only Forms builds are not sold as durable core products.
Small internal products for owners, managers, and staff who need clearer records without buying a GUI-only workflow nobody can reproduce.
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 CLI-ready handover.
Dummy-data examples of internal tools that can be read, tested, deployed, and maintained through CLI/API workflows.
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, or API-first platform 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.
Apply the CLI test. If an agent cannot create, update, test, and deploy it through CLI/API, I do not treat it as the core build.
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 / CLI-operable Tool / Client-owned Deployment decisions.