Turn a business idea into a website, app, or mini program ready to launch.
Product strategy, interface design, engineering, testing, and release—led by one accountable product partner.
Clear starting scopes
Lead-generation websites from $3,000. Mini program and mobile web projects from $3,000–$5,000. App MVP engagements from $12,000.
Selected work
Delivered products, working MVPs, live tools, and clearly labeled independent product concepts across gaming, local services, education, productivity, healthcare, finance, hospitality, logistics, property, and creative operations.
Detailed case studies
Playmate
Delivered product · US gaming startup · Phased multi-platform MVP · duration not publicly disclosed
PlayMate brings player discovery, social activity, messaging, booking, and payment into one product. The marketplace serves two distinct audiences: players looking for a reliable companion and verified companions managing services, availability, orders, and earnings.
We treated trust as part of the core transaction rather than a separate policy page. Verification, service pricing, order status, protected payment, refunds, disputes, and reviews are surfaced at the moments when users need them.
Business problem
A gaming marketplace can feel active without feeling safe. The product had to preserve the energy of gaming culture while making identity, service scope, availability, and payment protection easy to understand.
Product decisions
We mapped the complete player and companion journeys first, then built shared product rules for profiles, discovery, community posts, chat, orders, and settlement. The web platform and React Native app use the same product model while adapting navigation and density to each device.
Scope delivered
- Player and verified-companion account systems with distinct permissions
- Discovery across 20 launch games, with filters for rank, role, language, price, and availability
- Protected order flow covering booking, service delivery, completion, reviews, refunds, and disputes
- Responsive web product, shared iOS/Android codebase, operations console, and TestFlight delivery workflow
Current outcome
The core marketplace, community, order, payment, and operations workflows are implemented. The responsive web release is available; the shared iOS/Android build is in the TestFlight delivery stage.
Homi
Delivered product · California home-services operator · MVP delivered to TestFlight · duration not publicly disclosed
Homi turns an open-ended request for household help into a clear, bookable service. Customers can compare service types, configure the size and condition of a home, select a time and address, pay at booking, and follow the job through completion.
The product was designed for San Jose, the wider Bay Area, and Los Angeles. English and Simplified Chinese were planned together so service names, pricing explanations, booking states, and support messages remain understandable in either language.
Business problem
Home-service pricing depends on details that customers do not always know how to describe. The booking experience needed enough structure to quote and schedule accurately without turning the flow into a long questionnaire.
Product decisions
We organized the journey around progressive decisions: service, home details, add-ons, time, address, and payment. Reusable status components then connect booking confirmation, professional assignment, arrival, completion, cancellation, and refund information.
Scope delivered
- Bilingual service catalog and location-aware customer experience
- Configurable booking flow for home size, rooms, service level, and add-ons
- Immediate payment, order tracking, professional messaging, ratings, and after-service support
- Responsive web release, iOS packaging, automated regression coverage, and TestFlight Build 4
Current outcome
The complete booking path—from service selection to payment and order tracking—was delivered as a responsive web product and an isolated iOS test build. TestFlight Build 4 is available for internal device testing.
一纸昕意
Working MVP · In-house product development · Native iPad MVP · duration not publicly disclosed
一纸昕意 is built for students who write with Apple Pencil but still need the structure of a digital course archive. Notes are organized by quarter, project, folder, and page, with continuous vertical paging for long classroom sessions.
Its defining interaction is “handwriting as directory.” A student can write a chapter title naturally, turn it into a two-level index, and return to the exact page later. Recording, transcription, PDF annotation, inserted media, and recovery tools support the rest of the study workflow.
Business problem
Most note apps make students choose between freeform handwriting and rigid organization. The goal was to introduce structure without interrupting the writing rhythm or covering the page with desktop-style controls.
Product decisions
We designed around the iPad canvas first: Apple Pencil tools stay close at hand, the directory resizes the page instead of obscuring it, and file operations use familiar long-press and batch patterns. Data persistence, recently deleted items, and iCloud recovery were treated as core study features.
Scope delivered
- Apple Pencil writing, eraser, lasso, undo/redo, and continuous vertical pages
- Handwritten chapter titles converted into a two-level navigable directory
- PDF import/export, annotation, recording, playback, and speech transcription
- Persistent course hierarchy with rename, move, copy, batch management, safe deletion, and recovery
Current outcome
A working native prototype can be installed and used on a physical iPad. The main classroom loop—organize a course, write with Apple Pencil, build a handwritten index, review recordings, and recover files—has been tested end to end.
Brainwave Nest
Live product · In-house shared tool · Live iterative release · duration not publicly disclosed
Brainwave Nest is a small shared workspace for two people, creators, students, or independent builders. Ideas are separated into product ideas and task ideas, then advanced through early thinking, testing, and outcome review.
Instead of replacing earlier notes, the product keeps intermediate thinking visible. Rich-text entries can be confirmed into reusable cards, reopened for revision, recovered from history, and exported as CSV when a more formal review is needed.
Business problem
Lightweight idea tools are easy to start but often lose the reasoning behind a decision. The product needed to remain playful and low-friction while preserving edits, experiments, and both successful and failed outcomes.
Product decisions
We retained the intimate pink-and-space visual language while giving each idea a clear state model. Cloudflare Worker and D1 provide a public shared data layer, and the responsive layout also works as an installable iOS web app.
Scope delivered
- Separate product-idea and task-idea workflows with unlimited entries
- Early idea, testing, success review, and failure review stages
- Rich-text editing, confirmed cards, deletion, revision history, and CSV export
- Public Cloudflare deployment with shared D1 data and iPhone-ready web-app behavior
Current outcome
The product is publicly accessible on Cloudflare and stores shared content in D1. It is used as a real, editable workspace rather than a static design prototype.
Mediflow
Independent product concept · Independent concept study · Concept scope · not launched · duration not published
MediFlow explores how a clinic can present providers, appointment availability, visit preparation, secure video care, and follow-up records as one continuous patient journey.
The interface prioritizes plain-language status, clinical hierarchy, and high-contrast actions. Patient-facing tasks remain distinct from the clinic workspace used to manage schedules, visit queues, and care follow-up.
Business problem
Remote care products carry dense information and high user anxiety. Patients need to know what happens next, while clinic teams need an operational view that does not expose internal complexity to the patient.
Product decisions
The concept separates patient and clinic permissions, defines a repeatable appointment state model, and uses bilingual content patterns for provider profiles, scheduling, consent, and visit instructions.
Scope delivered
- Patient and clinic role model
- Provider discovery, appointment selection, and visit preparation
- Secure-video visit flow and post-visit record structure
- English and Spanish interface system designed for responsive web and mobile
Current outcome
The result is a product-direction and interface study, not a commissioned client product. It demonstrates a plausible patient/clinic system; clinical compliance, integrations, and production validation remain outside this concept scope.
Northstar Finance
Independent product concept · Independent concept study · Concept scope · not launched · duration not published
Northstar Finance organizes accounts, transactions, recurring costs, budgets, and savings goals into a single household view. The emphasis is interpretation: users should understand why a balance changed and what commitments are coming next.
Charts are paired with category and transaction detail so the interface does not rely on color or trend lines alone. Forecasts are framed as planning aids rather than guarantees.
Business problem
Finance dashboards often show many numbers but provide little context. The concept needed to help users move from “what happened” to “what can I adjust” without presenting automated suggestions as financial advice.
Product decisions
We structured the dashboard around monthly cash flow, upcoming obligations, category variance, and goal progress. Drill-down patterns preserve the link between each summary number and its underlying transactions.
Scope delivered
- Unified accounts and transaction history
- Budget categories with planned-versus-actual context
- Savings-goal tracking and cash-flow forecast
- Responsive dashboard system for desktop and mobile
Current outcome
This is an interface and information-architecture study, not a live financial product. It tests how account data, budgets, goals, and forecasts could be connected; bank integrations and regulated financial services are not represented as delivered.
Tablemuse
Independent product concept · Independent concept study · Concept scope · not launched · duration not published
TableMuse combines the visual confidence of a dining guide with the practical detail of a reservation product. Guests can evaluate a restaurant, choose a seating time, understand menu and price expectations, and continue into pre-ordering when the venue supports it.
Restaurant imagery leads discovery, while availability, party size, dietary notes, cancellation terms, and order status are treated as transactional information that must remain easy to scan.
Business problem
Discovery interfaces encourage browsing, but booking interfaces demand precision. The concept needed to transition from editorial content to a committed reservation without a sudden change in tone or missing operational details.
Product decisions
We designed a shared restaurant object that supports story-led discovery and real-time booking data. Reservation, menu, payment, preparation, and arrival states follow a consistent progression.
Scope delivered
- Curated restaurant discovery and venue profiles
- Party-size and real-time availability selection
- Menu pre-ordering and payment flow
- Preparation, arrival, and order-status tracking
Current outcome
The concept validates the guest-facing journey and its visual direction. It does not claim live table inventory, restaurant partnerships, or a production payment integration.
Fleetarc
Independent product concept · Independent concept study · Concept scope · not launched · duration not published
FleetArc connects dispatchers, drivers, vehicles, routes, and shipment milestones in a real-time operations workspace. The central map is supported by a prioritized exception queue so teams can see delays, missed scans, route changes, and driver availability without monitoring every shipment manually.
The driver experience is intentionally narrower: assigned stops, navigation handoff, proof of delivery, status updates, and direct contact with dispatch.
Business problem
A map can show where vehicles are but not which issue deserves attention. The product concept had to turn live location and shipment events into a practical work queue for dispatch teams.
Product decisions
We defined shipment and route states first, then designed exception severity, ownership, and resolution patterns. Desktop density serves dispatch operations while the mobile workflow limits drivers to immediate route tasks.
Scope delivered
- Live fleet map with route and vehicle context
- Prioritized shipment exception queue and resolution history
- Driver status, stop sequence, navigation, and proof of delivery
- Operational reports for on-time performance and recurring delays
Current outcome
This work defines the operating model and responsive interface direction. Live telematics, carrier integrations, routing algorithms, and production field testing are intentionally outside the concept claim.
Keynest
Independent product concept · Independent concept study · Concept scope · not launched · duration not published
KeyNest centralizes portfolio health, rent collection, leases, maintenance, and tenant communication. Landlords see occupancy and open work across properties; tenants see only their home, balance, documents, and service requests.
Every maintenance request keeps the original report, images, assignment, visit schedule, status changes, and resolution together, reducing the ambiguity created by phone calls and separate message threads.
Business problem
Property communication is fragmented across payment portals, email, text messages, and contractor calls. The concept needed a shared record while keeping landlord, tenant, and service-provider permissions clearly separated.
Product decisions
We mapped the lease lifecycle and maintenance lifecycle as related but independent systems. Role-based dashboards surface the same underlying record differently for portfolio owners, tenants, and assigned providers.
Scope delivered
- Portfolio, occupancy, lease, and balance dashboard
- Tenant rent payment and receipt history
- Maintenance intake, assignment, scheduling, and resolution workflow
- Central message history and lease-document library
Current outcome
The deliverable is a role and workflow concept for property operations. Payment processing, identity checks, accounting integrations, and production tenancy data are not presented as completed work.
FrameTogether
Independent product concept · Independent concept study · Concept scope · not launched · duration not published
FrameTogether gives agencies and production teams one place to review video, compare versions, discuss exact moments, and record approval. Comments stay attached to a timestamp and version so feedback does not become detached from the work it refers to.
The workspace also separates active review from the broader asset library. Producers can manage source files, exports, owners, due dates, and approval states without crowding the focused playback experience used by clients and reviewers.
Business problem
Creative review breaks down when comments arrive in email, chat, and meetings while files continue to change. The concept needed to preserve context across versions and make final approval unambiguous.
Product decisions
We designed the data model around project, asset, version, timestamp, thread, and approval. The interface gives reviewers a simple playback-and-comment flow while exposing production controls only to the team managing delivery.
Scope delivered
- Timestamp comments and threaded discussion
- Version comparison with resolved and unresolved feedback
- Explicit review, change-requested, and approved states
- Central asset library and responsive desktop/tablet workspace
Current outcome
The concept documents the review model and responsive UI, but it is not represented as a production collaboration service. Media transcoding, storage infrastructure, permissions auditing, and load testing would be part of a later build phase.