[ Service · AI-driven development ]
Thoughtfully designed web services, built with AI-driven development for rapid delivery
I build new web services and MVPs with AI-driven development, using Claude Code and subagents for rapid delivery. The AI splits up research, implementation, and verification; I own the architecture, task breakdown, diff review, and security decisions. Because I can carry UX-minded UI design, code, infrastructure, billing, email, CI/CD, and launch through end to end, nothing gets lost in handoffs. I recently built and launched a B2B generative-AI web service in four business days.
What I can do for you
- Architecture for a new web service or MVP (screens, data, APIs, permissions)
- UX-minded UI design, and building it
- Serverless setups on Cloudflare Workers, D1, and R2
- Billing with Stripe
- Transactional email with Resend
- CI/CD with GitHub Actions and Wrangler
- Launch, and improvements after launch
Track record
- Built a B2B generative-AI web service (contract) in four business days; launched November 2026
- The client owned planning and requirements; as a team of two, we handled everything from architecture and UX-minded UI design to code, infrastructure, billing, email, CI/CD, and launch
- Stack: Cloudflare Workers (serverless), D1 (database), R2 (storage), Resend (email), Stripe (billing), GitHub Actions × Wrangler (CI/CD)
- Claude Code and subagents split research, implementation, and verification; I owned architecture, task breakdown, diff review, and security decisions
- Security rules for auth, input validation, and secret handling were documented for the AI to follow, and I reviewed every diff myself
How the approaches compare
| Traditional development | Leaving it all to AI | AI-driven development, with design and review kept human | |
|---|---|---|---|
| Speed | Every step needs hands, so it takes time | Code comes fast, but rework is common | Research, build, and verification run in parallel for rapid delivery to launch |
| Design consistency | Depends on who's on the team | Ad-hoc code creeps in | Architecture and task breakdown are decided by a human; AI works within them |
| Quality | Depends on the review process | Sometimes no one has read the generated code | Every diff is reviewed by a human before it's merged |
| Security | Depends on the developer's knowledge | Auth, input validation, and secret handling are easy to miss | Security rules are documented for the AI to follow, and the final call is human |
| UI/UX | Design and build are split, and intent can get lost | Looks polished, but user flows may not be thought through | UX-minded design is carried through to code by the same hands, so the intent survives |
How we'll work
- 01
Requirements
We go over what you want to build, who it's for, and when, and agree on the scope of the first release.
- 02
Architecture and task breakdown
I design screens, data, APIs, and permissions, and split the work into tasks the AI can take on.
- 03
Parallel build with subagents
Claude Code and subagents split research, implementation, and verification and run in parallel.
- 04
Diff review and security checks
I read every diff and check auth, input validation, and secret handling before it's merged.
- 05
Ship with CI/CD
GitHub Actions and Wrangler automate deployment through to launch.
FAQ
- Can I trust the quality and security of AI-written code?
- I don't hand the project over to AI. I decide the architecture and task breakdown, and I read every generated diff before it's merged. Rules for auth, input validation, and secret handling are documented for the AI to follow, and the final call is always mine.
- How much can I hand over to you?
- Architecture, UX-minded UI design, code, infrastructure, billing, email, CI/CD, and launch — I can handle all of it. If your idea or requirements aren't settled yet, we can start by shaping them together.
- Can you work on an existing service too?
- Yes. I review your current code and setup, then add features or make changes without breaking the existing design. Share what you have and I'll propose how to proceed.
- How long will it take?
- It depends on the scope, so I'll give you an estimate once I understand your requirements. Narrowing the first release is the surest way to ship quickly.
- Do you work in English and Japanese?
- Both. I'm a native Japanese speaker and work professionally in English, fully remote from Cebu, Philippines.
Want to get your new web service in front of users sooner?
Tell me what you want to build and when you'd like to launch. I'll reply within one business day.
Email mehello@yutahirano.com