Product architecture
How TipTop turns scattered PQQs into structured credibility.
A walk-through of the core flows, data model, and rules engine that power vendor prequalification, scoring and comparison.
01
Core flow
Vendor onboards
Account + company
Completes PQQ
6-section wizard
Structured store
Normalised data
Rules engine
VQI scoring
Client searches
Filter + facet
Compare 2–3
Side-by-side
Shortlist + decide
Saved evaluation
02
Personas
Vendor
- →Maintain a single credibility profile
- →Reuse PQQ data across clients
- →Improve VQI over time
Client
- →Find qualified vendors fast
- →Compare like-for-like data
- →Build defensible shortlists
Admin
- →Govern data quality
- →Tune scoring rules
- →Monitor activity
03
Data model
Vendor
- id
- name
- city, country
- headcount, founded
- sectors[]
- status
Capability
- disciplines[]
- internal vs subcontract
- equipment list
- automation level
Project
- name, type, scope
- value range
- year
- gmp flag
Compliance
- certifications[]
- gmp history
- audit log
- quality system
Capacity
- regions[]
- workload %
- availability
- resource pool
Score
- capability
- compliance
- capacity
- output
- VQI (derived)
04
Rules engine — Vendor Quality Index
Capability
35%
Disciplines, internal ratio
Compliance
30%
Certs, GMP, audits
Capacity
20%
Headcount, regions
Output
15%
Projects delivered
VQI = round(0.35·capability + 0.30·compliance + 0.20·capacity + 0.15·output)
Tier 1 · Preferred
≥ 85
Tier 2 · Qualified
70 – 84
Tier 3 · Conditional
< 70
05
System layers
Experience
React · TanStack Router · Tailwind v4 · shadcn/ui
Workflow
PQQ wizard · Comparison engine · Shortlist · Notifications
Domain
Vendor · Project · Compliance · Capacity · Score
Rules
VQI weights · Tier thresholds · Eligibility filters
Storage
Structured vendor records · Audit log · Versioned PQQs
Trust
Swiss data residency · RBAC (Vendor / Client / Admin)