CHOOSING AN AUTOMATION PARTNER

Choose the working relationship your project needs.

The right choice depends on the scope, the skills involved and who will operate the result. Here is what working directly with me involves, alongside two common alternatives.

ASK EVERY PROVIDER
01

Who is responsible?

Name the person building the system and the person supporting it.

02

What will be delivered?

Agree the scope, acceptance checks and handover.

03

What happens later?

Clarify ownership, change requests and support after launch.

PUT THE ANSWERS IN THE AGREED SCOPE
Work directly with HeshamAn agreed scope and fixed priceCode and infrastructure you own

OPTION 01

An independent specialist

A good fit when the brief is already defined and you can lead the project.

WHAT TO CLARIFY

Ask who will do the work, how changes are priced, and what support is included.

THE ARRANGEMENT

Provider and contract terms vary. A marketplace can help you find and compare candidates.

OPTION 02

An agency team

A good fit when the project needs several disciplines or sustained delivery capacity.

WHAT TO CLARIFY

Ask who is assigned, who makes technical decisions, and how the team handles handover.

THE ARRANGEMENT

The breadth of the team can be useful; make ownership and ongoing support explicit.

OPTION 03

Direct with Hesham

A good fit when you want one builder to diagnose, implement and maintain an AI content system.

WHAT TO CLARIFY

Start with a $1,500 diagnostic, credited toward a fixed-price build from $5,000.

THE ARRANGEMENT

You work directly with me. Code and infrastructure stay on accounts you control; ongoing support is scoped separately.

BEFORE YOU COMMIT

Four things to put in writing.

These are useful questions whether you hire through a marketplace, choose an agency or work with me.

SCOPE

What does completion mean?

Define the workflow, expected outputs and examples that the build must handle.

  • Named deliverables and dependencies
  • Acceptance checks using representative data
  • A process for changes outside the agreed scope

OWNERSHIP

What can you take with you?

Confirm access to the workflows, source code, deployment accounts and documentation.

  • Accounts and credentials under your control
  • Third-party licences and recurring costs identified
  • A handover another builder can understand

OPERATIONS

Who responds when a run fails?

Agree what monitoring exists and what support you are buying.

  • Clear alerts and a recovery procedure
  • An explicit support scope and response arrangement
  • A route for maintenance and upgrades

FIT

Has the provider solved a related problem?

Examine the work and ask how it relates to your constraints.

  • A relevant workflow or architecture example
  • Clear distinction between a prototype and a deployed system
  • A discussion of tradeoffs and limitations

WORKING TOGETHER

What working directly with me costs.

The free call is an introduction. The diagnostic is the paid engagement that defines the build.

01 / DIAGNOSTIC

Find the right first build.

Map the workflow, its constraints and the work worth doing. You receive a prioritised plan and a fixed-price scope.

$1,500Credited toward the build

03 / ONGOING SUPPORT

Keep a named person involved.

Optional monitoring, fixes and improvements from the person who built the system. The support scope is agreed separately.

Scoped to your systemOptional after launch

TAKE IT INTO THE CONVERSATION

Ask better questions before you hire.

A printable checklist for comparing an automation consultant, freelancer or agency. Use the same questions with every provider, including me.

48 questions across scope, architecture, data access, testing, ownership, pricing, support and handover. Space to record the answers and the evidence you want to see.

3 pages · Printable PDF · Free · No email required

First page of the automation provider checklist
FAQ

Questions about hiring direct

What changes when there is no platform in between.

What does a project cost?
Who actually does the work?
What happens after launch?
How fast can we start?
Do you build on n8n specifically?
Can you migrate us from Zapier or Make?
Cloud n8n or self-hosted?
When does a build need Cloudflare instead of n8n?
Do I own what you build?
Where are you based?
Are you insured, and will you sign an NDA?
How can I check your credentials without marketplace reviews?

See whether the project fits a direct engagement.

A short conversation is enough to understand the workflow and decide on a sensible next step.