How apptivando/onconciliaweb works
OnConcilia’s repository is primarily its beta-acquisition landing page and supporting sales materials, not the bank-reconciliation application itself. The evidenced user path is visitor → landing page → beta form → external CRM, which can return an appointment URL. The repository also contains structured prospect/sales types, SQL schemas, email templates, and internal strategy and sales content; their runtime connections are not demonstrated by the sampled excerpts, so those relationships are left out.
Main entry points: BetaForm.tsx Beta signup form · page.tsx Beta landing · layout.tsx Site layout
Components 12
Beta website
- Beta landing
src/app/page.tsx - Beta signup form
src/components/BetaForm.tsx - Site layout
src/app/layout.tsx
Sales materials
- Sales objections
src/lib/objeciones.ts - Sales document catalog
src/lib/documentos.ts - Sales and strategy content
content - Outreach email templates
emails
Prospect CRM model
- Prospect data types
src/lib/types.ts - Prospect database schemas
supabase/prospectos.sql
Other components
- Prospective customer
- Apptivando CRM
- CRM appointment page
Connections 6
- Prospective customer → Beta landing: visits
src/app/page.tsx - Beta landing → Beta signup form: renders
src/app/page.tsx - Beta signup form → Apptivando CRM: submits lead
src/components/BetaForm.tsx - Apptivando CRM → Beta signup form: returns appointment URL
src/components/BetaForm.tsx - Beta signup form → CRM appointment page: redirects
src/components/BetaForm.tsx - Site layout → Beta landing: wraps page
src/app/layout.tsx