Custom Web-Based Sales System for Car Dealership

We are a Swedish online used-car dealership and we want to build a custom internal sales system (web-based) to handle our sales workflow with a strong focus on:
• Creating deals from our vehicle inventory
• Generating sales contracts
• Digital signing (BankID + e-sign provider)
• Creating and sending invoices
• Pulling vehicle + customer data via integrations

You will receive a test login to our current sales system (read-only for reference) so you can replicate the key workflows and UX patterns.

Scope (MVP first)

1) Deal / Sales Workflow
• Create a “Deal” connected to a vehicle (registration number / regnr)
• Attach a customer to the deal (private individual)
• Set price, add-ons, notes, and basic deal statuses (e.g., Draft → Sent for signing → Signed → Invoiced)

2) Contract Generation + Signing
• Generate a contract PDF (template-based)
• Send for digital signing via:
• BankID signing integration
• Scrive integration (use their APIs for e-signing workflows)
• Store signed documents and maintain a complete audit trail (timestamps, status, signer identity confirmation)

3) Invoice Module
• Create invoice from an approved/signed deal
• Send invoice to customer (email delivery is enough for MVP)
• Store invoice PDF and status (Draft/Sent/Paid – “Paid” can be manual in MVP)

Required Integrations

Airtable (mandatory)

We already use Airtable heavily and the new system must integrate with it to pull:
• Vehicle registration number (regnr)
• Pricing and key vehicle fields
• Optional: vehicle status and internal notes

We want a stable sync approach (API-based) with clear mapping. Airtable can remain the source of truth for vehicle inventory in the MVP.

Vehicle Data Lookup (mandatory)
• car.info integration to fetch car details by registration number (regnr)
(We will provide access details/requirements as needed.)

Customer Credit/Identity Data (mandatory)
• UC integration to retrieve customer information based on Swedish personal identity number (personnummer)

Signing (mandatory)
• BankID integration for signing (directly or via an e-sign provider flow—open to your recommendation)
• Scrive integration for digital contract signing

Note: We will provide any necessary credentials/partner access and expect the developer to implement against official APIs/SDKs.

Key Requirements
• Web app, responsive (works well on desktop + mobile)
• User authentication + roles (Sales rep / Admin)
• Full activity log / audit trail per deal (important for compliance)
• GDPR-minded handling of personal data (access control, logging, data minimization)
• Clean UI focused on speed (sales reps must work fast)

Deliverables
1. Technical plan + architecture (short but clear)
2. Working MVP deployed to our environment (or your suggested hosting setup)
3. Documented setup instructions + API keys/config management
4. Basic automated tests (at least for core flows)
5. Post-launch support for a short stabilization period

Tech Preferences (flexible)
• Modern web stack (React/Next.js or similar)
• Backend with a clean API (Node/Python/.NET are all acceptable)
• Database: Postgres preferred
• Must support integration work (webhooks, background jobs, retries, logging)

We are open to your recommendations as long as it’s stable and maintainable.

How We Want to Work
• We want milestone-based delivery with demos.
• Weekly progress updates (short and concrete).
• You will get access to a reference system via login to understand the expected workflow.

What to Include in Your Proposal

Please answer briefly:
1. Relevant projects you’ve built (CRMs, contract/signing flows, invoicing, integrations)
2. Your experience with BankID, Scrive, Airtable API, and UC (or similar regulated integrations)
3. Your proposed stack and why
4. A milestone plan for the MVP (2–4 milestones is fine)
5. Estimated timeline and budget range