Ignitor CRM.
Your workflow connected.
Built around your business.
Anviam developed Ignitor CRM from scratch with PHP/Laravel, Vue.js and MySQL, connecting CRM configuration, lead acquisition, email engagement and sales pipeline workflows.
From lead acquisition
to coordinated follow-up.
- Built from scratch
- PHP / Laravel
- Vue.js frontend
- MySQL data
Conceptual workflow illustration · Not a product screenshot
From Lead Capture to Connected Business Workflows
- The productA custom CRM for acquisition, sales and operational activity.
- Anviam's contributionPHP/Laravel, Vue.js and MySQL development from scratch.
- The purposeConnect lead context, engagement and opportunity progression.
A Custom CRM Shaped Around Business Workflows
Anviam developed Ignitor CRM from scratch using PHP/Laravel, Vue.js and MySQL, bringing CRM configuration, lead acquisition, email engagement and opportunity management into one business application.
Product Context
A custom CRM for managing acquisition, sales and related delivery activities, configured around how each business actually works.
Users and Responsibilities
Sales teams need organised lead context and clear opportunity status. Marketing users need acquisition and engagement workflows; managers need operational visibility.
Connecting Acquisition, Engagement and Sales Progression
Requirements that follow from the product scope, not a reconstructed history of incidents.
Lead Context Across Channels
Leads from different sources need consistent identity and source information. Duplicates and missing attribution make follow-up harder to coordinate.
Configuration Without Confusion
Custom fields, interfaces and workflows need clear validation and ownership, so flexibility never leaves teams unsure which information is required.
Visible Opportunity Progression
Pipeline stages need understandable meaning and next actions, so users can tell an active opportunity from a stalled or completed one.
Sales-to-Delivery Continuity
Where delivery and time management are enabled, the product needs an explicit handoff from the sales workflow and reliable status context.
PHP/Laravel, Vue.js and MySQL, Built From Scratch
The application was developed from scratch using the stack supplied directly for this case study.
Custom Application Development
Developed the CRM from scratch around the product requirements.
PHP / Laravel Backend
Backend business rules, validation and application workflows built with PHP and Laravel.
Vue.js Frontend
CRM navigation, readable record information and clear workflow states built with Vue.js.
MySQL Data Layer
Relationships between contacts, acquisition context and business workflows, held in MySQL.
CRM Configuration, Acquisition and Pipeline Management
Features from the supplied project information; plan entitlements were not independently verified.
Acquire
- Campaign landing pages for lead acquisition
- Multi-channel lead management
- Email marketing and engagement
Sell
- Advanced pipeline management
- Opportunity tracking through sales stages
- Custom CRM interface and workflows
Deliver
- Delivery phase management (Enterprise)
- Time management (Enterprise)
- Dashboards for CRM activity
Capture the Lead. Coordinate Follow-Up. Progress the Opportunity.
A conceptual business journey based on the feature list, not an inspected sequence of screens.
Configure the CRM
Set the interface and workflows around the intended business process.
Create the campaign
Prepare a landing page for the acquisition campaign.
Capture the lead
Bring the enquiry into the relevant lead workflow.
Review context
Check source and contact information before follow-up.
Engage by email
Use the email workflow with the right preferences and permissions.
Progress the opportunity
Update pipeline context as the sales conversation develops.
Record the outcome
Mark the opportunity outcome when the conversation concludes.
Coordinate delivery
Where Enterprise capabilities are enabled, manage delivery and time.
Review the dashboard
Understand activity and outstanding work across the CRM.
A Custom Application With Connected Records and Workflows
Engineering considerations relevant to the stack and features; internal implementation was not inspected.
Lead identity and source handling
Define duplicate detection, source attribution and record ownership, without assuming a particular channel connector or attribution model.
Configurable workflows
Agree field types, validation and configuration changes, and preserve meaning when a business process or required field changes.
Landing pages and lead capture
Define how submissions enter CRM records, how failures are surfaced and how unwanted submissions are handled.
Email engagement state
Separate queued, sent, delivered and response states where supported, with clear provider responsibilities and suppression rules.
Pipeline and delivery transitions
Define stage changes and handoff criteria against the business workflow, with explicit acceptance criteria for delivery and time capabilities.
Laravel, Vue.js and MySQL boundaries
Keep request validation, record permissions and frontend status consistent across the stack.
A Custom-Built Foundation for CRM Operations
The engagement joins PHP/Laravel, Vue.js and MySQL development in a CRM built from scratch.
Useful measures include lead completeness, duplicates, follow-up time, stage progression and handoff errors. No conversion lift, sales growth or productivity figure is claimed.
Connected Business Capability
Acquisition, engagement and opportunity progression connected with operational CRM information.
Contact Privacy and Responsible Marketing Workflows
Requirements depend on the market, contact data and campaign activity. No independent compliance audit or certification is claimed.
Contact and Lead Information
Collection purposes, lawful processing, notices, access and retention under applicable privacy law, including UK GDPR.
Email Marketing and Preferences
Consent or other marketing conditions, sender identification, preferences and suppression, including UK PECR.
Campaign Tracking and Cookies
Landing-page analytics, tracking technologies and preference requirements assessed for each campaign.
CRM Record Access
Staff access, record ownership and least privilege across the interface and backend.
Providers and Integrations
Email, hosting and channel-provider processing arrangements and data transfers.
Retention and Operational Records
Retention and deletion for lead, campaign, opportunity and time records, reconciled with marketing preferences.
Why Anviam for Your Custom CRM Project?
Bring custom application development together with the acquisition, sales and operational workflows your business needs. See our enterprise software and SaaS services.
Talk Through Your Project- Development from scratch: a custom CRM application, not an off-the-shelf configuration.
- PHP / Laravel experience for business rules, validation and workflows.
- Vue.js frontend delivery for records, pipeline information and next actions.
- MySQL application data linking contacts, acquisition and workflows.
- Lead acquisition and engagement: campaigns, channels and email as one requirement.
- Pipeline-to-delivery thinking, including the handoff into delivery work.
- Dashboard and activity visibility around meaningful operational information.
- Evidence-led acceptance criteria agreed before claiming growth or efficiency.
Sources and evidence
Development scope, features and plan descriptions were supplied directly for this case study. No authenticated workflow, source code or campaign analytics were inspected. Delivery-phase and time management are labelled as Enterprise capabilities.