Your business already runs on a system. It is just made of people.

Parking and reservations, from one screen

Every guest existed three times: the reservation sheet, the parking sheet, and an email about payment. Keeping them in agreement was a daily manual job.

• One linked base. Reservations, parking and payments joined, so a guest is one record everywhere.
• Payment collection that runs itself. A checkout link per guest, validated before issue, and the record updates the moment payment lands.
• A next action engine. Each record states what it needs now, so the day is a queue rather than a judgement call.

What has stood out most is the breadth of his capabilities and his ability to bring different systems together coherently rather than treating each tool or integration as a separate problem. […] He tests thoroughly, documents clearly, and is good at tracing issues to the right layer of the system rather than treating symptoms superficially.

Every lead, and what each one cost

Leads came from a form, tracked calls and Meta ads, none of which talked to each other. Ad spend sat elsewhere again, so cost per customer was a monthly guess.

• One lead database. All three channels write to the same table with the source attached.
• Duplicate detection. Numbers normalised before matching, so a repeat caller updates the record that exists.
• Self healing credentials. Ad connections refresh their own tokens, so the system does not silently die every sixty days.

From day one he understood exactly what I was trying to build and got it done without me having to hold his hand or repeat myself. […] If you need Airtable work done right the first time by someone who actually cares about the outcome, hire him.

From enquiry to enrolled, without re-typing

Every student was keyed in three or four times across booking, payment and the learning portal, so admin time was becoming the ceiling on intake size.

• Payment driven progression. Card and direct debit from two providers move a student forward automatically.
• Rule based cohort routing. Students placed into the right intake and level by the system, not by admin judgement.
• A clean handover layer. Confirmed students pass to the third party portal team through a structured exchange, with no manual exports.

A repeatable process, without a person driving it

A well understood production process done entirely by hand. Throughput was capped by headcount, and consistency depended on whoever picked the job up.

• One request, one document. A task in the tool the team already uses produces a finished document, nothing copied by hand.
• Separated stages, not one instruction. Each step runs under its own rules, so any stage can be corrected without rebuilding the rest.
• A draft, not a publication. Output lands in the team's own documents. It removes the blank page, not the writer.

Usama is an exceptional N8N developer who consistently went above and beyond to deliver outstanding results. […] Even when unexpected issues arose, Usama tackled them head-on - troubleshooting, problem-solving, and even rebuilding parts of the workflow when necessary.