BUSINESS TOOLS / WEB PROJECT
Pest control. Precisely planned.
FumiCare combines a distinctive pest-control website with a connected service-workflow prototype. Ten tailored service forms lead into reviewed quotes, customer workspaces, coordinated visits and released service reports. The public fumicare.ng address currently presents a construction page; the complete application and payment simulations are developed and tested locally.
PROJECT SCOPE
01 / THE BRIEF
Design a recognisable pest-control website and demonstrate the whole journey from a reported property concern to an agreed service and a recorded visit. Keep the questions specific to each service, make unknown scope easy to report, and connect customer, operations and technician views around the same records.
02 / THE APPROACH
Deep blue-black, vivid lime, chalk surfaces and amber details give FumiCare a precise, field-led identity. An original perimeter-and-pest emblem, diagrammatic service artwork and an AI-generated illustrative inspection scene support the property-first presentation. The application separates enquiry, quote, order, payment, visit and report states. A React interface connects to a native Node.js API and a persistent SQLite database, with validated intake, versioned scope records and role-based access. The public construction release is deployed separately on Cloudflare, while live payments and the operational application remain outside that release.
03 / THE EXPERIENCE
A custom pest-and-perimeter emblem, bold typography, lime highlights and deep ink surfaces create a distinctive service brand. Ten original SVG plates connect pest concerns with property contexts. The inspection photograph is an AI-generated illustration, rather than evidence of a completed job.
General pest control, fumigation, termites, rodents, mosquitoes, cockroaches, ants, bed bugs, preventive inspection and commercial management each have a dedicated intake. A four-step flow adapts questions to the reported concern and property; unknown measurements can remain unknown and route to assessment. Recoverable device drafts and server validation keep the enquiry consistent.
Google Places suggestions begin after three characters and are restricted to Nigeria. Selecting a result fills the address, city, state or FCT and a hidden coordinate pair. Editing location details clears the previous coordinates; each commercial site keeps its own location. Manual entry remains available if lookup fails. This integration belongs to the local application.
A commercial enquiry can describe multiple properties, operating hours, access and documentation needs. Each site receives independent quote revisions and a separate single-site order, so accepting the scope for one property does not prevent another from being reviewed. The stored site snapshot follows its own quote and order.
Operations staff prepare itemised quotes with scope, inclusions, exclusions and expiry. Customers can accept or decline the current version. Superseded or expired quotes cannot be accepted; custom amounts require a recorded reason. An accepted order preserves its service, intake, quote and payment-plan snapshots instead of changing when later configuration is edited.
The local test configuration demonstrates direct checkout for four bounded service cases and a separate preventive-inspection purchase. The server calculates the offer from the current rules, stores a 15-minute preview and requires a new review when rules change. Unknown, unsupported or out-of-scope cases route to review. Inspection purchases cover inspection only; later treatment needs a separate agreement.
An internal test adapter demonstrates full payment, a configured deposit, separate balance collection and pending, failed or successful attempts. Pending attempts are reconciled before another is opened, and verified simulation events create deduplicated acknowledgments. No real charge, card collection or automatic balance payment occurs; a live payment provider is not connected.
Customers see their own enquiries, quotes, orders, payment acknowledgments, visits and released reports. They can ask for help or request a change, cancellation, reschedule, additional work or a privacy review. Requests enter a staff-review workflow. Record ownership is checked by the server, and staff-only report content is kept out of the customer view.
A future morning or afternoon preference in Africa/Lagos time is a request, rather than a confirmed slot. Staff confirm the visit and assign a technician; overlapping assignments are rejected. Customer coordination acknowledgments and the technician's separate readiness check precede starting work. A simulated payment cannot override a blocked visit.
Assigned technicians record findings, work done, remaining work and follow-up. A submitted report goes through staff approval and release before the customer can view it. Corrections retain the previous version and require a reason after approval. Remaining work keeps the order open; protected device drafts help technicians resume an unfinished report.
Customer, operations, administrator and assigned-technician permissions separate personal records, service queues and configuration. Staff review enquiries, quotes, visits, requests and basic metrics. Administrators can edit draft descriptions, test rate components and local eligibility or payment settings with a recorded reason; account deactivation revokes its sessions. These are prototype operations, not a live service launch.
SQLite migrations, relational constraints and transaction-wrapped changes connect service snapshots, checkout offers, quotes, orders, visits and report versions. Idempotent retries avoid duplicate commitments and acknowledgments. Audit events and a deduplicated local notification outbox retain the activity trail. External email and SMS delivery are not connected.
04 / WEB TECHNOLOGY
05 / INTEGRATIONS
A server-side adapter provides Nigeria-restricted suggestions and selected-place details with Google Maps attribution, request budgets and manual fallback. Real Abuja address selection was verified in the source project. The public construction page does not perform address lookup.
The native Node SQLite module persists related records, quote versions, expiring checkout previews, audit events and accepted snapshots. SQL migrations preserve existing records between local application updates.
Local test outcomes exercise payment schedules, reconciliation and acknowledgments without contacting a payment provider. Live payment collection is not enabled, and no provider configuration is implied by the prototype.
Persistent, event-deduplicated notices and local delivery retries support the workflow demonstration. No external email or SMS provider is connected.
fumicare.ng and its www hostname serve a separate public construction release. Only its approved static assets are published; booking, account and staff routes return to the landing page, while API and write requests remain closed.
CURRENTLY FULLY BOOKED