Built and operated the software behind a Belgian lead-generation business for five years.

How a €2,000 project became five years of work

The first job was small: a webhook, an admin tool for landing pages and a basic Laravel application. It was worth roughly €2,000.

The client’s business kept changing. New lead sources appeared. Customer requirements changed. Integrations became necessary. Features that mattered in one version of the business stopped mattering in the next. That first build gradually became the software behind the operation, and I became the external senior developer responsible for moving it forward.

What ownership meant

There was no frozen five-year specification. The work was to understand each new commercial or operational problem and then decide what the software needed next.

That included building new features, rewriting earlier ones when the business model changed, removing features that had become obsolete, fixing production problems, connecting third-party systems and keeping the important flows visible. The value was not just knowing Laravel. It was holding enough context to make practical decisions without the founder having to translate every business problem into a technical task.

The system that grew around the business

• Lead intake from six-plus sources. Each source supplied different fields and changed in different ways. Incoming data had to become consistent before anything downstream could rely on it.
• Distribution and CRM integrations. Leads had to reach the right broker and fit the way that broker actually used its CRM — which was often different from the way the CRM expected to be used.
• Custom billing and reporting. The platform connected activity in the lead flow to the commercial administration around it.
• Lifecycle email. A contact base of more than 100,000 records had to be segmented using project, lead and behaviour data, then processed reliably through queues.
• Internal dashboards, queues and monitoring. The operational team needed to see what was happening, and failures needed to become visible before they turned into silent data loss.

The awkward part: real-world integrations

The hardest work was rarely a single algorithm. It was the mismatch between systems and between the people using them.

Every CRM uses words such as “lead”, “contact” and “deal” differently. Clients configure the same CRM in different ways, and some use it for a workflow it was never designed for. Real-estate data is similarly inconsistent: a project can be one home, a whole building or a set of unit types, with different fields per country, source and client.

Keeping one clean internal model made that variation manageable. The platform absorbed the messy inputs and produced the exact output each customer integration required.

The outcome

For five years, the platform processed thousands of leads per month and supported the company’s day-to-day operation while the business kept changing around it.

That is the strongest kind of proof I can offer: not a polished one-off launch, but a revenue-critical Laravel system another business trusted me to keep building, fixing and operating over years.