Systems

What I have built.

Five products designed, built and operated independently — four of them taking real payments, one in private beta — plus three further products in production that carry less weight here. Each case study gives the problem, the architecture, the domain model, the hard decisions and the current status. Every product states its state; no invented metrics.

TaxFintech

Atamatax

US expat tax infrastructure

In production · payments live

Explore the system Visit site

Problem: Americans abroad carry fragmented US obligations — FBAR, PFIC rules, Form 8621, catch-up procedures — hidden inside ordinary foreign accounts and funds; the market offers a specialist at several thousand dollars, or nothing.
System: Tax situation engine · document workflow · fixed-price fulfillment
Role: Research, product, rules engine, engineering, payments, search acquisition
Hardest part: Making uncertainty honest: every classification carries its source, a confidence level and the assumption still to confirm — and never reads as a legal determination.

ConsumerLegal rules

Horvera

Flight compensation infrastructure

In production · payments live

Explore the system Visit site

Problem: A disrupted passenger does not know air law and should not have to; the market answer is a claims company that keeps 30 to 44% of the payout.
System: Deterministic rules engine · claim workflow · programmatic search
Role: Research, product, rules engine, engineering, payments, programmatic search
Hardest part: Three jurisdictions that share one text and diverge on amounts, currencies and the reading of delay — carried by one versioned engine that shows its trace and its sources.

ConsumerTests

Wabiro

Identity and relationship tests built for search and sharing

In production · payments live

Explore the system Visit site

Problem: Personality and relationship tests are a huge search category built on forced sign-ups, endless quizzes and results with no method.
System: Test engine · versioned scoring · share loop · one-off payments
Role: Research, product, scoring systems, engineering, payments, SEO acquisition
Hardest part: Holding the privacy line — answers never leave the device — while still allowing sharing, head-to-heads and paid reports.

B2BProduct security

Vellaci

EU Cyber Resilience Act compliance for product manufacturers

In production · subscriptions live

Explore the system Visit site

Problem: The EU Cyber Resilience Act turns product security into questions with legal deadlines — what is exposed, what must be reported inside 24 and 72 hours, what evidence can be produced — and most manufacturers answer them from spreadsheets and ticket timestamps.
System: SBOM ingestion · vulnerability intelligence · deadline engine · evidence vault
Role: Research, product, regulatory modelling, engineering, payments, search acquisition
Hardest part: A reporting clock a regulator will accept: it starts when a named reviewer confirms awareness with a rationale — not when a ticket was created — and it is computed server-side with its rule version, source timestamp and timezone persisted, never only in the browser.

Creator EconomyPricing

SponsorsMetrics

The pricing cockpit for YouTube talent agents

Private beta · design partners onboarding

Explore the system Visit site

Problem: YouTube talent agents in France price sponsorships by feel; when a brand says “too expensive”, there is no external comparable to answer with.
System: YouTube API pipeline · CPM benchmark · deal desk · subscription billing
Role: Product, engineering, design, pricing-data pipeline
Hardest part: Bootstrapping a data product: the benchmark is only worth something once real campaigns are connected — hence a private beta with design partners before open access.

Also built and operated

A system to build?

Six questions to place your project, then a free scope review.

Check project fit

danilson.daveigaramos.pro@gmail.com · Reply within 24h, Mon–Fri.