Dimore Connect
Field teams log every architect meeting, sample handover and project specification; managers see conversion across ten sales tiers in real time.
- ClientDimore Surfaces
- IndustryManufacturing
- CountryIndia
- PlatformAndroid app + Web admin
- Launched2026
- Built withLaravel, PHP, MySQL, JWT, Firebase, Vultr S3
The client
Dimore Connect is the field sales and reporting platform of Dimore Surfaces, a premium surfaces and luxury tile manufacturer. Its sales model runs on relationships with architects, interior designers, commercial builders and certified dealers across many Indian states, and the app is where every one of those relationships is now recorded.
Sales teams log meetings, specifications and architect-driven leads in one place, and managers follow pipeline movement and conversion performance in real time. ATOA designed the backend architecture, the REST API used by the mobile app and the web admin portal behind it.
The challenge
Before Dimore Connect, management had no real-time view of field work: daily visits, follow-up commitments and the handover of sample binders and surface test kits lived in spreadsheets and paper logs. A sales structure of six sales tiers (L1 to L6) and four business development tiers (B1 to B4) had no unified reporting line.
Architects specify surfaces early in the design phase, but without a central pipeline those specifications were often lost by the time the contractor placed the order, and high-value projects slipped away.
The product master catalogue holds thousands of sizes, finishes and price points. Mixing that catalogue traffic with high-volume meeting logs in a single database created heavy server load and slow responses for reps in the field.
Every lead, architect and report had to follow a recursive supervision tree, so that each manager from L2 to L6 and B2 to B4 sees and reallocates exactly the downline that reports to them, and nothing else.
From the architect's first meeting to the dealer's order
We built a Laravel 12 backend with a dual-database architecture: operational data (users, meetings, specifications, notifications, approvals) in one MySQL database and the product catalogue (brands, products, sizes, finishes, variant maps) in another, linked through cross-connection Eloquent relationships.
The mobile REST API uses JWT authentication with sliding token refresh, documents and floor plans go to S3-compatible Vultr object storage, and scheduled jobs send a daily 8:00 PM push reminder through Firebase Cloud Messaging to reps with pending reports and clean up rejected leads every week.
Architect lifecycle
A 5-stage onboarding flow with manager approvals and push alerts.
Project specifications
Residential and commercial projects tracked from design to procurement.
Meeting and sample tracker
Daily visits and sample kit handovers, with an 8:00 PM reminder.
Conversion analytics
Negotiation, won and lost ratios by state, dealer and sales tier.
Inside the sales platform
Every new architect checked before they count
When a field executive registers an architect, the request lands with their manager as an Architect Details card: name, firm, address, contact number, type, category such as interior designer, and who requested it. The manager can edit the details, then approve or reject in one tap, and approved architects move to the Assigned list with the executive they belong to, so the architect master stays clean across every tier.
- Architect name, firm and address
- Contact number, type and category
- Requested by, for every new entry
- Edit details, approve or reject
- Assigned list with the owner of each architect
See every architect by status and by team member
The architect list can be cut by status, All, Pending, Assigned, Unassigned and Unallocated, with a coloured badge on every card. Managers also switch to Team members and pick a person from their downline to see only that executive's architects. Every card shows the firm, who it is assigned to and the address, the search finds an architect by name, and the plus button adds a new one from the field.
- Filters for pending, assigned, unassigned and unallocated
- Coloured status badge on every architect
- Team member view for managers
- Assigned to and address on each card
- Search by name and add from the field
Log a meeting in under a minute
Add Meeting starts with who it was with, an architect, a dealer or a customer. The rep picks the name, the firm fills itself in, then they add who it is assigned to, the agenda, the brand products discussed, the meeting date and the next follow-up date. Meetings can only be logged within four days, so entries stay honest, and the meeting list filters by date on a calendar for quick reviews.
- Meetings with architects, dealers or customers
- Firm name filled in automatically
- Agenda and brand products discussed
- Meeting date and next follow-up date
- Calendar filter on the meetings list
What changed for Dimore Surfaces
- 10 sales tiers in one reporting hierarchy (L1 to L6, B1 to B4)
- 100% field activity reported in the app, no spreadsheets or paper logs
Management now sees daily field activity across every tier in real time, project specifications are followed from the architect's design stage to dealer fulfilment, and architects and dealers can be reallocated across branches in seconds instead of days.
Also built for Dimore Surfaces
Dimore Radar App
Field-audit app: the photo team captures dealer showrooms, branding and compliance documents, synced instantly to the admin portal.
View case study →
Dimore Insight App
Flutter app for the field sales team and a Laravel admin that tracks sales by zone and region and calculates incentives automatically.
View case study →
Qutone OT
Stock and sales app for Qutone Ceramic: live stock across 50,000+ SKUs, instant PDF quotations and ERP sync for 100+ field reps.
View case study →