Bubllio CRM pilot roadmap

Pilot targetCopy Anchor Link

A small organism, agency, IT provider or MSP must be able to:

1. organise companies and people,
2. monitor sales opportunities,
3. Knows what action needs to be taken next,
4. manage the active services of his clients;
5. Knows which recurring charges expire or delay;
6. operated safely in self-hosted facility.

What's already workingCopy Anchor Link

• Workspaces, applications, memberships and role-based missions.
• Tenant isolation for organization-owned data.
• Companies with customer code, owner, lifecycle stage, archive and activity.
• Contacts with company, owner, primary contact, archive and activity.
• Deals with pipeline, drag and drop, status, owner, contact, probability, date of closure, VAT and lost reason.
• Tasks and follow-ups with company/contact/deal, owner, due time, reminder, priority, date-based list, workflow board with drag and drop and next action in deals.
• Services, subscriptions, renewals, internal charges and recurring revenues.
• Actionable Overview with personal tasks, overdue follow-ups and billing attention.
• Organization and ERP defaults.
• SMTP account configuration.
• Basic automations and automation runs.
• Installation administration, production-readiness checks, backup status, local data export and GitHub update notifications.
• Business and technical documentation for the above.

P0 — Required for pilotCopy Anchor Link

1. Single customer and deal timelineCopy Anchor Link

Chronological view of changes, notes, completed tasks, contacts, deals and services/payments. Timeline must separate system events from human actions and not store sensitive old values without reason.

** Result:** any member of the team immediately understands what has happened with a client.

2. Global searchCopy Anchor Link

Search in companies, customer codes, contacts, email, phone and deals, always within the user's authorized workspaces.

** Result:** Quick access to unsearched registrations on different pages.

3. CSV importCopy Anchor Link

Import companies and contacts with preview, column mapping, validation, duplicate checks, error report and identifiable import batch.

** Result:** a customer pilot can start with its existing data without manual re-entry.

P1 — Differentiation and daily valueCopy Anchor Link

4. Saved views and My workCopy Anchor Link

My companies, my deals, closing this month, no next action, overdue follow-ups, renewals and archived records.

5. Deal profileCopy Anchor Link

Full deal page with timeline, stage history, notes, activities, contacts and next action. The existing drager remains the fast creation/edit flow.

Off PilotCopy Anchor Link

• AI lead scoring and general AI functions without measurable need.
• Marketing campaigns and mass email marketing.
• Helpdesk/ticketing.
• Official pricing, accounting and myDATA.
• Advanced forecasting, quotas and territory management.
• Custom field builder and fully customizable pipelines.
• Multiple price books and CPQ.
• Full inbox/calendar synchronization.
• Native mobile application.

These can be re-evaluated after a real pilot feedback.

Agreed rowCopy Anchor Link

Unified timeline
  -> Global search
  -> CSV import
  -> Saved views + My work
  -> Deal profile
  -> Pilot hardening and onboarding

The series can only be changed when customer pilot confirms that different workflow is more important. Scope does not change because one feature exists in another CRM.

Definition of DoneCopy Anchor Link

Each feature shall be considered complete only when it has:

• short business problems and user flow,
• clear in-scope and out-of-scope behavior,
• documented domain model and tenant ownership,
• permissions and cross-tenant validation,
• migrations for every model change,
• business logistics in services/models and not in loaded views,
• API tests for success, validation, performances and tenant isolation,
• frontend loading, empty, error, disabled and success states,
• responsive and keyboard-accessible interaction,
• use of mature UI libraries instead of custom primitives where appropriate solution,
• Django checks, division composition, division tests, frontend lint and production build,
• updated technical and non-technical documentation,
• gitmoji commit with clean working tree.

Quality ruleCopy Anchor Link

Implementation does not start before the problem, data, edge cases and acceptance criteria are agreed. We do not define planned as functional and do not implicitly extend the product to accounting, support or marketing system.