Live cross-device beta
The mobile and desktop application surfaces are live and use a shared account state.
Privacy-first net worth application
PecuIQ: a privacy-first net worth tracker app. Built around honest records.
What does PecuIQ wealth-tracking application do, and who is it for?
PecuIQ is a live privacy-first wealth-tracking beta built around manual net-worth records, conversational onboarding and observational insights. The work combines product strategy, responsive app engineering, mobile and desktop parity, import and synchronisation safeguards, brand design and careful non-advisory language. The intended operating context is Mobile web, desktop web, PWA, backend sync and design system. Thomas's role was Founder, product director and application builder. The case follows the product from its main operating problem through Live cross-device beta, Conversational first use, Mobile insight parity, then connects each interface to a working feature and control. The evidence comes from live releases, application tests, browser qa and design prototypes. It also records what failed, what changed and how privacy, evidence or approval boundaries are handled. The limit is explicit: tracking evidence only, with no financial-advice or user-growth claim.
StatusLive beta
RoleFounder, product director and application builder
ScopeMobile web, desktop web, PWA, backend sync and design system
EvidenceLive releases, application tests, browser QA and design prototypes
Known limitTracking evidence only, with no financial-advice or user-growth claim
Public proof / Last verified 4 September 2026View PecuIQ
01 / The operating problem
A finance product had to feel intelligent without pretending to be an adviser.
A direct account of the operating constraint, the product decision and the limits of the evidence.
Net worth is a simple equation, but a trustworthy product has to handle edits, histories, deletions, imports, offline use, account switches and two devices changing the same state. A beautiful total is useless if an old cloud snapshot can silently overwrite a recent local record.
The product also needed a careful role for AI. Conversational onboarding can make first use easier, and Insights can reflect patterns in a person's own numbers. That does not justify investment recommendations, return projections or language that implies a financial outcome.
PecuIQ was therefore designed as a tracking product with a visible data-health model. Mobile and desktop share core behaviours, imports explain uncertainty, synchronisation fails visibly, and observations stay descriptive. The longer financial-OS roadmap is separated from what the current beta can prove.
| Primary job | Give a person one clear, current view of assets, liabilities and net worth. |
|---|---|
| Product premise | Manual entry first, AI-led onboarding, privacy and understandable records. |
| Working surfaces | Mobile and desktop app, PWA install, Insights, imports, history and account controls. |
| Language boundary | Observations about the user's own data, never product recommendations or promised returns. |
| Public evidence | Synthetic holdings and values in every screen. |
02 / What changed
PecuIQ wealth-tracking application: shipped product behaviour.
These are observed properties of the working system. They are not claimed percentages, revenue attribution or a guarantee of future performance.
Conversational first use
A staged AI-led onboarding flow turns rough asset and liability answers into an understandable starting dashboard.
Mobile insight parity
Observational Insights are available on mobile rather than existing only on the desktop surface.
Stronger data integrity
Reload, deletion, account-switch, offline and import failures were found, fixed and converted into checks.
Installable product
PWA caching, self-hosted type and valid platform icons support an intentional installed experience.
Clear advice boundary
The interface reflects the user's own records and avoids recommendations, forecasts or guaranteed milestones.
03 / Interface tour
Screens, states and responsive views in PecuIQ wealth-tracking application.
Every image preserves the interface purpose and control logic while replacing live people, projects, records and values with staged data.
04 / Feature evidence
Explore the evidence for PecuIQ wealth-tracking application.
Each entry links to the exact view it describes. Product captures and explanatory diagrams retain their own evidence labels.
Actual product capture / generic data
Current net-worth home
What this evidence shows
The live product preview uses synthetic holdings and adapts to a purpose-built mobile app view.
Actual product capture / generic data
Conversational onboarding
What this evidence shows
A guided conversation turns best estimates into a draft financial picture that can be checked before it is saved.
Actual product capture / generic data
Data health and reconciliation
What this evidence shows
Source health, missing records and import uncertainty stay visible before the product accepts a total as current.
Actual product capture / generic data
Holdings and value history
What this evidence shows
Assets and liabilities keep editable records and history so a change can be explained rather than hidden inside one total.
Actual product capture / generic data
Observational insights
What this evidence shows
Insights describe patterns in the user's own staged records without recommending products or forecasting returns.
Explanatory system diagram
Feature map
What this evidence shows
A visual summary connects the main product capabilities to the decisions, controls and user outcomes they support.
Explanatory system diagram
End-to-end workflow
What this evidence shows
The complete working sequence shows how information moves from the first input to a checked and reviewable outcome.
05 / System design
Product logic, data and release layers behind PecuIQ wealth-tracking application.
The visible dashboard is only the decision surface. Context, data, permissions, review and learning determine whether it can be trusted.
Holdings model
Assets, liabilities, values and history preserve the records needed to explain the total.
Experience layer
AI onboarding, Home, Assets, Liabilities, History and Insights form a direct product journey.
Sync and account layer
Cloud state, pending writes, deletion and account changes use explicit safeguards and recovery paths.
Import and data health
Reconciliation, debt-free cases, locale-aware numbers and uncertainty remain visible before data is accepted.
Brand system
A dark-first gradient identity, tabular numbers, motion rules and reusable components keep product states consistent.
06 / Working flow
From user input to useful feedback in PecuIQ wealth-tracking application.
A useful workflow names the input, owner, check, approval boundary and proof that closes the loop.
Start
Pecu asks short questions and accepts best estimates without implying false precision.
Record
The person adds or imports assets and liabilities with source and edit context.
Reconcile
The product flags ambiguity, locale or missing-debt conditions before accepting the total.
Observe
Dashboard, history and Insights describe changes and concentration in the person's own data.
Protect
Synchronisation, wipe, sign-out and offline paths preserve clear account and device boundaries.
07 / Working features
Working product features inside PecuIQ wealth-tracking application.
Each feature exists because it changes a decision, reduces unsafe ambiguity or makes a failure easier to see.
AI onboarding
A seven-scene conversation captures currency, property, investments and liabilities before revealing the dashboard.
Net-worth home
Total, assets, liabilities, allocation and recent change stay readable without dashboard overload.
Holdings and history
Assets and liabilities can be edited with value history, charts and safe delete behaviour.
Observational Insights
Trend, cash, concentration, liability and milestone cards reflect the user's own data without advice.
Import and reconciliation
Locale-aware numbers, ambiguous totals and debt-free cases are reviewed before merge.
Cross-device safeguards
Account switching, offline use, pending writes, wipe recovery and service-worker rules are verified.
08 / Issues and changes
Product failures and regression fixes in PecuIQ wealth-tracking application.
The strongest evidence in an operating system is often the failure behaviour. These issues became design constraints and regression checks.
History loss
What failed
Per-item value history could disappear after a reload.
What changed
Persist and reconstruct history through the shared data layer, then verify it across mobile and desktop.
False deletion
What failed
A desktop wipe could clear the device while cloud records returned on reload.
What changed
Use an explicit pending wipe and durable remote deletion path before confirming success.
Save-then-leave loss
What failed
A quick close or account event could happen before a delayed write completed.
What changed
Track pending state, serialize pushes and recover unsent work before the next cloud load.
Debt-free import block
What failed
A user with no debt could be prevented from importing a valid record.
What changed
Show an acknowledgement and preserve the unusual but valid case instead of hard-blocking it.
Mobile and desktop drift
What failed
Important safety fixes could land on one surface only.
What changed
Add parity markers and consistency checks that fail the build when required behaviour diverges.
09 / Controls and limits
What PecuIQ wealth-tracking application proves, and what it does not.
A public case study should make it easy to see what is working, what remains internal and what has not been proven.
Known limit
Tracking evidence only, with no financial-advice or user-growth claim.
The visuals use public route captures and real public app screens with synthetic values. The product tracks information; it does not provide financial advice or prove a user outcome.
10 / Capabilities demonstrated
Capabilities demonstrated by PecuIQ wealth-tracking application.
Strategy, interface, governance and implementation are treated as one operating problem rather than separate deliverables.
11 / Follow the evidence
Evidence connected to PecuIQ wealth-tracking application.
Each link adds a different layer of first-hand evidence rather than repeating the same page under another keyword.
12 / Clear answers
PecuIQ wealth-tracking application: practical questions and answers.
Practical answers about the build, its use and its limits.
Is PecuIQ live?
Yes. A mobile and desktop beta is live.
Does PecuIQ provide financial advice?
No. The current product tracks records and presents observations about the user's own data.
Are the values in these images real?
No. All holdings, history and net-worth values are synthetic.
Is the full financial OS roadmap already built?
No. The case separates current beta evidence from later cashflow and education ideas.
Need a data product people can trust?
Product strategy, Fintech UX, App build, AI onboarding
A product diagnostic, critical-flow prototype and evidence-backed build plan. Handover: the findings, a prioritised plan and the evidence needed to decide the next step. Scope and schedule are agreed after the fit conversation.
Live releases, application tests, browser QA and design prototypes
Product strategy / Fintech UX / App build
Need a data product people can trust?
Thomas can shape the product, interface, evidence model and recovery behaviour around the decisions your users actually make.