Andrew Furusawa

Andrew Furusawa

Product & Software Delivery Consulting

Inland Empire, CA

12+ years shipping multi-platform mobile and web software across healthcare, consumer IoT, and education.

Certified Scrum Product Owner badge, Scrum Alliance

Certified Scrum Product Owner · Scrum Alliance, 2026

Make the problem clear before the code gets expensive.

I turn ambiguous requirements into shipped software. I run discovery with the people who use the product, write the user stories and acceptance criteria that keep a team pointed at the right thing, and stay close enough to the code to know what a request actually costs.

  • Clarify

    • Discovery
    • User research
    • Usability testing

  • Define

    • Wireframes
    • PRDs
    • Acceptance criteria

  • Deliver

    • Production code
    • Tests
    • Documentation
    • Handoff

Where I help

Most wasted engineering effort traces back to a requirement everyone thought they understood the same way.

  • Getting the right thing built

    I sit between stakeholders and engineering so the wrong thing doesn't get built. I turn what people say they want into what the software has to do, and surface the assumptions nobody stated — validated against real users through discovery and usability testing before it gets expensive to change. Information architecture, wireframes, and prototypes come out of that work.

  • Building it the way a team would

    Those become PRDs, user stories, and acceptance criteria, and then I build against them with agentic tooling — which is where the speed comes from. The process underneath stays what any team would run: code standards, code review, branch strategy, CI/CD, decision records, and a test strategy that decides what actually warrants coverage instead of chasing a percentage.

  • Multi-platform delivery

    Web, iOS, and Android from one codebase — React and Next.js, Ionic and Angular, or Flutter, chosen to fit what your team already runs. That includes moving an existing app onto a modern stack without stopping delivery.

  • AI inside the product

    Where AI belongs in the product itself, I handle feasibility research, prompt architecture, and production implementation on a provider-agnostic foundation — so you're not locked into whichever model is winning this quarter.

Recent work

Three engagements, most recent first.

AI debate practice platform 2026–present
MilkTracker 2020–2024
Blossom / GroConnect 2017–2020
2017now

AI debate practice platform

Education

2026–present

Independent consultant

Took an AI debate-practice product from an open feasibility question to a working application, solo — prompt architecture that holds models to each phase of a round, and judge scoring paradigms converted into a usable rubric.

  • <1 wkWorking prototype in under a week, provider-agnostic across two model vendors
  • 2 daysSpeech in and out added in two days, paced to competition time limits
  • Opposing models able to debate each other, with phase timers and live user-vs-model rounds
  • Next.js
  • React
  • Typescript
  • Tailwind CSS

MilkTracker

Healthcare

2020–2024

Lead front-end developer · AngelEye Health

Hired to maintain a legacy Objective-C iOS app, I proposed and led the multi-platform rework that replaced it — one Angular and Ionic codebase across web, iOS and Android.

  • 10+In production across more than ten hospitals nationwide, up from three
  • Eliminated a recurring scanner licensing cost by implementing barcode scanning natively
  • Introduced the development process, documentation and specifications the team had been operating without
  • Angular
  • Ionic
  • Typescript
  • ReactiveX
  • Jasmine

Blossom / GroConnect

Consumer IoT

2017–2020

Lead mobile app developer · Scotts Miracle-Gro

Led a distributed front-end and QA team on connected-device apps, inheriting a smart-irrigation controller at acquisition and unifying the device family under one app platform.

  • 70%Load time improved by over 70% for 20,000+ users within months of the acquisition
  • Consolidated a fragmented smart-gardening device portfolio into one app platform
  • A shared Flutter library standardising future lawn-care applications onto one framework
  • Ionic
  • Cordova
  • Angular
  • Typescript
  • Bitrise

How I work

Discovery first.

Engagements start with a short paid discovery sprint. I dig into the problem, prove or disprove the risky assumption, and come back with a plan and a realistic scope. Small commitment for you, and the larger engagement gets built on something real.

Sprint-based, not spec-based.

Product work rarely survives a fixed specification, because you learn what's possible by building it. Short cycles, each with a working deliverable and written acceptance criteria, mean you see progress as it happens instead of finding out at the end. Neither of us wants a surprise on delivery day.

Handoff is the deliverable.

Every engagement ends with documentation, specifications, and a codebase your team can maintain.

Writing

All writing

Contact

Tell me what's stuck. The first step is a short discovery sprint, and a short email is enough to start it.