Thai Dinh Chinh CV
All work
Project Management · Product Analysis

Rofarez — IoT security products, from prototype pitch to delivery

Turning ideas for IoT security products into prototypes the CEO and I pitch to clients, then into scoped, scheduled deliveries — owning product analysis, the team and the timeline across four countries.

Rofarez — IoT security products, from prototype pitch to delivery
Role
IT BA & Project Coordinator — PM scope
Timeline
03/2026 – Present
Team
12–15 cross-functional
Clients
Vietnam · Malaysia · Singapore · US
Domain
IoT security — location tracking · movement monitoring · 3D modelling
Context

IoT security products for clients in four countries

Rofarez builds IoT-based security solutions — location tracking, movement monitoring and 3D modelling/visualisation of physical spaces — for clients in Vietnam, Malaysia, Singapore and the US. Ideas typically start as a client conversation or the CEO's vision, not a specification.

I own the path from that idea to a delivered product: product analysis and direction, the prototype used to pitch, and the team and timeline that deliver it. Tools: Jira, Miro, Figma, Power BI.

Problem

Prove the idea fast, choose the right stack, keep four time zones on one plan

  • Clients commit to something they can see and touch — early-stage ideas needed a convincing, testable prototype before any spec existed.
  • Hardware, software and market move together: sensors and devices, platforms and integration options had to be researched against market trends before committing the team.
  • Several client projects run in parallel across four countries; a 12–15 member team needs unambiguous priorities and a timeline that survives change.
  • Delivery, UAT and defects across projects had to stay visible to management and clients at the same time.
My role

Product analysis, prototype & pitch, team & timeline

  • Product analysis & direction: research technology, hardware, software and market trends; recommend the product direction and the solution options behind it.
  • Prototype & pitch: build the prototype for the whole project — user flows, UX/UI and an interactive demo — and pitch it together with the CEO to clients.
  • Team & timeline management: plan and run the 12–15 member team: scope, backlog, sprint execution, task allocation, risk and dependency tracking, milestone reporting.
  • Requirements & acceptance: user stories, business rules and acceptance criteria; UAT coordination, defect triage and release tracking.
  • Stakeholder alignment: keep clients, Product, Design and Engineering aligned on scope, priorities and trade-offs across time zones.
Process

From idea to delivered product

STEP 01

Research

Technology, hardware, software and market-trend research; solution options with feasibility and cost.

STEP 02

Direction

Product analysis → recommended direction, scope boundaries and success criteria agreed with the CEO.

STEP 03

Prototype

User flows in Miro, interactive UX/UI prototype in Figma covering the full product, not just a screen.

STEP 04

Pitch

Present the prototype with the CEO to the client; capture feedback and lock scope.

STEP 05

Plan

Timeline, milestones, team allocation and dependencies; sprint-ready backlog in Jira.

STEP 06

Deliver

Sprint execution, daily unblocking, UAT with the client, defect triage and release tracking; status reporting.

Artifacts

What I produce on a typical engagement

Research & product-direction briefsTechnology, hardware and market findings; recommended direction and options.
Interactive prototype + pitchFull-product Figma prototype and the deck used with the CEO in client pitches.
User-flow mapsEnd-to-end flows per persona, including device, edge and error paths.
Project plan & timelineMilestones, team allocation, dependencies and risks.
Sprint-ready backlogUser stories with business rules and acceptance criteria in Jira.
UAT plans, defect logs & release reportsTest scenarios per story, triage, release readiness and status for management.

Client work is under NDA — artifacts are described rather than shown. Sanitised samples available on request.

Outcome

One owner from idea to release

4
countries of active client engagement
12–15
team members and one timeline
3
solution areas: tracking · movement · 3D modelling
E2E
research → prototype → pitch → delivery

Clients see a working prototype before they commit and a single point of contact who understands both their business and the hardware/software constraints; the team gets a direction, a plan and a backlog that are ready to build.

Learnings

What this role taught me

  • A prototype is the fastest requirements document — clients react to screens and devices, not to paragraphs.
  • Researching hardware and market trends before promising a solution is the difference between a confident timeline and a hopeful one.
  • With stakeholders in four time zones, decisions must be written down the moment they are made — otherwise they get re-opened overnight.