Build Supabase B2B Sales Platform
Budget / Salary€250–750
TypeFreelance project
LocationRemote
Posted2 hours ago
The app we want to build
A B2B prospecting and sales management platform built on Supabase.
We want to organise healthcare companies and contacts, prepare campaigns for each market, and turn replies into sales opportunities with a clear owner and follow-up. La Pastilla will be the first team to use the app.
A complete record for each company
Distributors, manufacturers and end customers, with their contacts, countries, represented brands, documents and history. Include data imports and detection of potential duplicates.
Find the right audience
Filter by country, sector, language, owner and interest. Save segments and review each campaign’s recipients, applying exclusions and unsubscribe requests.
Manage opportunities as a team
Link emails, tasks and opportunities. Show the stage, owner and next action, with dashboards for activity and results by market.
Use the prototype as the design reference
Keep the prototype’s visual identity and navigation. The app will provide shared data, access for multiple users, and a Spanish and English interface for desktop and mobile.
MEDCOMBO · Development brief · 18 November 2026
How it will be built with Supabase
Supabase will be the technical foundation. The developer will build the interface, business rules and connections to external services.
Data and automation
PostgreSQL will store companies, people, segments, campaigns, messages, opportunities and tasks. Edge Functions will run server operations; Cron and Queues will organise scheduled and pending jobs.
Users and private files
Supabase Auth will manage sign-in. Row Level Security (RLS) policies will restrict records by organisation, role and assignment. Storage will hold private files; external service credentials will remain on the server.
Integrations the developer must build
Gmail: link conversations and capture replies. Sales email: schedule delivery with sending limits, unsubscribe handling and duplicate prevention. Odoo: exchange contacts and sales references. AI: summarise and classify enquiries, and suggest owners or draft replies.
The web interface will be hosted separately. Email delivery and AI will use external services with separate costs. La Pastilla will control the Supabase account and source code.
MEDCOMBO · Development brief · 18 November 2026
What we need from the developer
We request a phased proposal, with a usable release at the end of each stage. The prototype will be the reference for agreeing the screens.
First release
An app connected to Supabase: sign-in, permissions, companies, contacts, records, imports, search, filters and private documents. The team must be able to work with the same shared information.
Second release
Segments, templates, scheduled campaigns, Gmail integration, reply tracking, opportunities and tasks. Include campaign approval, pausing and exclusions checked before sending.
Third release
Odoo synchronisation, AI classification and summaries, advanced assignment and automated follow-ups. Quote agent access through an API as an optional extension.
How we will verify the app
Two users see the same shared data, each with access limited to their permissions.
Importing the same file again does not create duplicates; private files remain protected.
A campaign keeps its approved message and respects pauses, unsubscribes and sending limits.
A reply is linked to its contact and opportunity; retries do not cause duplicate emails.
What the quotation must include
Price and timeline for each phase; monthly costs for Supabase, hosting and integrations; assigned team; testing, training and support. Deliver source code, database schema, RLS policies, and deployment and recovery documentation.
Before contracting, agree the user count, data and email volumes, mailboxes, assignment rules and scope of each integration.
A B2B prospecting and sales management platform built on Supabase.
We want to organise healthcare companies and contacts, prepare campaigns for each market, and turn replies into sales opportunities with a clear owner and follow-up. La Pastilla will be the first team to use the app.
A complete record for each company
Distributors, manufacturers and end customers, with their contacts, countries, represented brands, documents and history. Include data imports and detection of potential duplicates.
Find the right audience
Filter by country, sector, language, owner and interest. Save segments and review each campaign’s recipients, applying exclusions and unsubscribe requests.
Manage opportunities as a team
Link emails, tasks and opportunities. Show the stage, owner and next action, with dashboards for activity and results by market.
Use the prototype as the design reference
Keep the prototype’s visual identity and navigation. The app will provide shared data, access for multiple users, and a Spanish and English interface for desktop and mobile.
MEDCOMBO · Development brief · 18 November 2026
How it will be built with Supabase
Supabase will be the technical foundation. The developer will build the interface, business rules and connections to external services.
Data and automation
PostgreSQL will store companies, people, segments, campaigns, messages, opportunities and tasks. Edge Functions will run server operations; Cron and Queues will organise scheduled and pending jobs.
Users and private files
Supabase Auth will manage sign-in. Row Level Security (RLS) policies will restrict records by organisation, role and assignment. Storage will hold private files; external service credentials will remain on the server.
Integrations the developer must build
Gmail: link conversations and capture replies. Sales email: schedule delivery with sending limits, unsubscribe handling and duplicate prevention. Odoo: exchange contacts and sales references. AI: summarise and classify enquiries, and suggest owners or draft replies.
The web interface will be hosted separately. Email delivery and AI will use external services with separate costs. La Pastilla will control the Supabase account and source code.
MEDCOMBO · Development brief · 18 November 2026
What we need from the developer
We request a phased proposal, with a usable release at the end of each stage. The prototype will be the reference for agreeing the screens.
First release
An app connected to Supabase: sign-in, permissions, companies, contacts, records, imports, search, filters and private documents. The team must be able to work with the same shared information.
Second release
Segments, templates, scheduled campaigns, Gmail integration, reply tracking, opportunities and tasks. Include campaign approval, pausing and exclusions checked before sending.
Third release
Odoo synchronisation, AI classification and summaries, advanced assignment and automated follow-ups. Quote agent access through an API as an optional extension.
How we will verify the app
Two users see the same shared data, each with access limited to their permissions.
Importing the same file again does not create duplicates; private files remain protected.
A campaign keeps its approved message and respects pauses, unsubscribes and sending limits.
A reply is linked to its contact and opportunity; retries do not cause duplicate emails.
What the quotation must include
Price and timeline for each phase; monthly costs for Supabase, hosting and integrations; assigned team; testing, training and support. Deliver source code, database schema, RLS policies, and deployment and recovery documentation.
Before contracting, agree the user count, data and email volumes, mailboxes, assignment rules and scope of each integration.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.