Jamil Fayad

Independent developer · Lebanon & remote GCC delivery

Custom software for the workflow your existing tools cannot handle.

I build web applications, internal tools and operational dashboards for businesses in Lebanon and remote teams across the GCC. The project starts with the people using the system, the business rules it must follow and the information it needs to connect.

Discuss your project

Share a short outline. I’ll review the fit, discuss your tools and requirements, then propose a paid scope before implementation.

See my independent GPS vehicle-tracking project →

Start with the business problem.

Custom software is useful when a critical workflow no longer fits the tools available to your team. It is not always the first choice: configuring an existing product or building a small integration can be more practical. Discovery should establish that choice before a large build is agreed.

What we can scope

  • Client portals and structured application intake
  • Internal dashboards and operational reporting
  • Custom booking or request-management applications
  • APIs and integrations between business systems

What the delivery can include

  • Defined users, permissions, workflows and acceptance criteria
  • A scoped interface, API and database design
  • Working releases and checks against the agreed requirements
  • Deployment, documentation and an explicit handover/support scope

What shapes the project quote?

  • User roles, screens, business rules and reporting requirements
  • Integrations, data migration and the condition of an existing codebase
  • Testing, deployment environments, documentation and support expectations

Scope and boundaries

The agreed release should name its features and acceptance checks. Data cleanup, third-party licenses, hosting and later features are scoped separately where needed. Discovery may recommend configuring an existing product instead of commissioning a custom build.

Is this a useful first project?

A useful brief names the users, the current workaround and the decision or task the software should improve. Include existing tools, necessary integrations, available data and any deadline. Unknown requirements can be resolved through a smaller discovery phase.

Relevant engineering work

The portfolio documents a food-recognition application developed as a master's thesis and an independent GPS vehicle-tracking project. Their project type and Jamil's contribution remain explicit; they are not repackaged as unrelated business-client case studies.

Read the GPS vehicle tracking project walkthrough →Explore the project portfolio →

Before we start

Which technologies do you work with?
The current portfolio includes Python, Django REST, React, PostgreSQL, Azure and Firebase. Technology selection should follow the application's requirements and the team's ability to operate it.
Who owns the code and accounts?
Repository access, infrastructure accounts, documentation, licensing and handover should be written into the agreed scope. Bring any ownership or procurement requirements to the first discussion.
How is a project priced?
A quote depends on the features, integrations, data migration, testing and support your application needs. Smaller improvements and focused projects are welcome; we can agree a practical scope before work starts.

Bring a workflow or application brief.

Share your company, current tools and the work you want to improve. Smaller projects are welcome. We can discuss fit, scope, integrations and a quote before work starts.

Describe your project