Data Product Builder
I’m Dan. I connect data, business logic, and thoughtful interfaces so people can search, compare, explore, and make informed decisions.
Comparison tools · Research platforms · Data applications
01 / Selected work
Three data-driven products I designed and developed in full. Explore how each turns complex information into an interactive experience.
View screenshot ↗A retirement comparison product that organizes country criteria into rankings and side-by-side views, with results that respond to passport and life-stage inputs.
My role · Full design & development
Visit thonretire.com (opens in a new tab)
View screenshot ↗A relocation research product connecting nationality, destination, and purpose. Structured topics become a conditional decision flow with relevant next steps.
My role · Full design & development
Visit thonexpat.com (opens in a new tab)
View screenshot ↗A research product organizing geographic indicators and time series into explorable tables and interactive chart views.
My role · Full design & development
Visit thoninvest.com (opens in a new tab)02 / What I build
Start with the question your customers or team need to answer. The data and interface follow from there.
Turn scattered records into a searchable resource with useful filters, clear categories, and meaningful detail pages.
Directories · Research platforms · Data-driven pagesHelp users weigh options or find a relevant path through explicit criteria, conditional rules, and understandable results.
Side-by-side comparisons · Ranking logic · Guided flowsGive teams a practical way to inspect indicators, explore trends, and work with structured information.
Interactive charts · Internal tools · Focused MVPsDefine the schema, prepare usable records, and plan how data enters and updates in the product. API connections, databases, and refresh workflows are scoped around your sources.
Cleaning · Normalization · Data models · APIsAlready have a product? I also take on scoped interface fixes, feature improvements, and technical SEO work.
The whole path
I work backward from the task: what should someone be able to find, understand, or decide?
Review available sources and usage rights. Define acquisition, cleaning, normalization, relationships, and storage appropriate to the scope.
Agree on rules and example results, then connect them to search, filters, comparisons, or visualizations.
Validate the agreed workflows, document the data model and update path, and prepare the product for its target environment.
Start focused. Build forward.
A small engagement should deliver something you can use and a clear basis for what comes next.
A bounded dataset, a consistent schema, documented transformations, and a clear product direction.
Start with the data ↗One dataset and one focused user flow: search, filter, compare, or explore.
Make it interactive ↗A scoped MVP connecting data, business rules, and a responsive interface, with an agreed delivery and update plan.
Scope a product ↗Multiple sources, scheduled updates, custom databases, and API-powered applications begin with a source and feasibility review. Price, milestones, and operating costs are agreed before work starts.
03 / How I work
You work directly with me. Each stage makes the next decision easier to review.
Agree on the audience, the decision to support, available sources, and what a useful first version looks like.
Define fields, relationships, cleaning rules, and how missing or conflicting records should be handled.
Turn example inputs and expected outputs into an interface you can try and refine.
Review acceptance examples, hand over code and documentation, and agree on deployment and ongoing updates.
The person behind the products
I designed and developed ThonRetire, ThonExpat, and ThonInvest from the ground up. They reflect the work I care about: making complex information easier to explore, compare, and use.
My approach connects data, product logic, and interface design around one question: what should this help someone do?
When we work together, you work directly with the person building your product—from shaping the first useful version to reviewing the details.
Tell me what you’re building04 / Good to know
A tool that makes information usable for a specific task. Examples include a searchable research library, a country comparison, a guided decision flow, or a dashboard that helps a team inspect its data.
No. Start with a sample and the sources you have. We can scope a data foundation first: structure, cleaning rules, and quality checks before committing to the full interface.
We can scope approved APIs, supplied files, and permitted data collection as part of the product. I review access, usage rights, source stability, and update requirements before confirming the approach.
Yes. One source, one dataset, and one user task is a useful starting point. Larger integrations, custom databases, and multi-workflow products use a separate scope and milestones.
We agree on sources, definitions, missing-data behavior, and example results. Data quality checks and traceable logic are part of the scope. Where specialist judgments are needed, the relevant domain expert must validate the rules.
You receive the agreed code, data documentation, and handoff. Hosting, refresh schedules, monitoring, maintenance, and new features are scoped explicitly; ongoing operation is not implied by the initial build.
Yes. I can review a specific interface issue, feature request, or technical SEO task. I confirm the existing setup and scope first. SEO work covers agreed technical improvements, with no ranking guarantee.
Both. We can discuss the product and work through requirements in English or Vietnamese.
Your next chapter
Tell me who will use the product, what information you have, and what they should be able to find or decide. A small, non-sensitive sample is enough to start the conversation.
Direct contact details will be added soon. If we’re already in touch, send your brief through that channel.
