Work What I Build How It Works For agencies Contact Book a 20-min call
AVAILABLE FOR SELECT WORK · TORONTOOPENAI SELECT PARTNER

Production systems, built end to end.

I’m Igor, a senior software engineer in Toronto. Fifteen years shipping Laravel/PHP and TypeScript/Node applications. My latest build is an AI messaging platform with validation, PII scrubbing, and human approval built into the send path — signed contract to first production release in eleven days.

Book a 20-min call Tell me about your project
OpenAI Select Partner Read the announcement
Laravel PHP TypeScript Node Next.js OpenAI Anthropic Twilio Stripe AWS

Agencies and consultancies: I also work white-label behind your brand.

Apps I've built

Shipped and running.

Two of them are the systems behind the proof videos above — real codebases, running live. Another is an earlier product with paying users.

CLIENT LAUNCH - 2026

Franklin Logistics - Courier Ordering Platform

Custom ordering platform for a Calgary courier company: server-authoritative quote engine, Stripe payments, driver dispatch with magic-link access, carrier-compliant Twilio SMS notifications, and automated e-Transfer reconciliation. From signed agreement to live customer orders in under a month.

Laravel PHP MySQL Stripe Twilio Mailgun
franklinlogistics.ca →

"Igor never simply delivered what we asked for—he consistently challenged us to think bigger. He offered thoughtful recommendations, creative solutions, and valuable insights that elevated our project far beyond what we had originally imagined. We wholeheartedly and without hesitation recommend him."

— Franco & Lyndon, Franklin Logistics
01

EstimateLane

Multi-tenant intake SaaS for electricians. Token-link request pages, file uploads, private operator inbox, SMS/email notifications, appointment reminders, request timelines.

Laravel Livewire Twilio Lookup Stripe Mailgun

Architecture behind the Client Intake walkthrough above.

estimatelane.com →
02

AmpedUpSites

Multi-tenant Laravel platform for prospect mining, personalized demo sites, private proposal pages, Stripe checkout, onboarding, lead capture, and operator review.

Laravel Horizon OpenAI Twilio Stripe Mailgun

Architecture behind the Agency Fulfillment walkthrough above.

Live demo →
03

AuthoritySitesAI

Earlier Laravel SaaS, different audience. Shows the platform-shipping pattern at scale.

1,065
paying users
2,144
sites generated
64,058
reviews processed

Earlier product, not actively marketed.

Proof — 04 walkthroughs

Watch the systems run.

Intake, fulfillment, reliability, and a Make bridge. Four short screen walkthroughs showing how I think about no-code orchestration, AI-assisted steps, backend logic, and clean handoff.

Proof-kit note EstimateLane and AmpedUpSites are real working apps I built. The businesses, people, and records shown in the walkthroughs are fictional demo data, so I can show the workflows without exposing client information.

Client Intake Workflow

EstimateLane · request link → file upload → owner inbox → SMS/email updates → AI-ready checklists → ready check

Customers submit, upload, and track a request from a private no-login page; the business gets an owner inbox, full timeline, and communication loop.

Intake Files SMS / email Private links Timeline

Agency Fulfillment Workflow

AmpedUpSites — prospect → demo → proposal → checkout → onboarding → operations

A repeatable agency offer with prospect tracking, generated assets, private proposals, Stripe handoff, tokenized onboarding, and operator dashboards.

Agency ops Proposals Onboarding Dashboards Stripe

Reliability / Error Handling Demo

Webhooks · retries · queues · logs · monitoring

Systems built to be supportable: background jobs, failed-job visibility, webhook history, retryable work, event timelines, and human review where needed.

Error handling Webhooks Retries Logs Human review

Make Bridge Demo

API event → Make webhook → routing → Sheets log → Gmail draft → error path

Make stays useful as the orchestration layer while API/backend logic handles state, routing, logs, edge cases, and handoff behind it.

Make.com Webhooks Sheets Gmail Error path

What I build

Behind your client offer.

Six things I get asked to build most. Pick one. Scope it. Ship it.

01

Intake and request flows

Structured forms, file uploads, private customer pages, owner/admin inboxes, and status timelines.

02

Internal dashboards and portals

Operator and client dashboards for portals, support teams, admins, fulfillment workflows, and handoff steps.

03

AI-assisted follow-up

OpenAI/Claude summaries, draft replies, classifications, reminders, human review steps, and safe notification loops.

04

Make/API/CRM bridges

API glue around Make, n8n, Zapier, HubSpot, GHL, Pipedrive, Airtable, Sheets, Stripe, Twilio, and client systems.

05

Document and file collection

No-login upload flows, missing-info requests, onboarding checklists, file review screens, and AI-ready summaries.

06

Reliability and handoff

Queues, retries, event logs, operator visibility, documentation, and screen walkthroughs.

How it works

How I work with partners.

Fixed scope. Existing stack respected. Documented handoff. You stay client-facing, I stay implementation-facing.

01

Map the workflow

We define the one workflow that matters: intake, quote, onboarding, follow-up, document collection, dashboard, or internal handoff.

02

Scope a fixed build

Clear deliverables, boundaries, tools, data flow, and handoff expectations — written down before code.

03

Build and connect

I build inside the chosen stack — Make, n8n, Zapier, Bubble, Supabase, HubSpot, GHL, Airtable, or custom API/backend pieces where useful.

04

Document and hand off

Working system, screen walkthrough, support notes, and a clean handoff so your agency keeps the client relationship.

White-label by default

White-label friendly by default.

Your agency keeps the client relationship. I work behind the scenes, respect the stack you already sold, join calls only when useful, document the build, record screen walkthroughs, and hand off the system cleanly.

You keep the client relationship

Your client knows your agency, not me — unless you introduce me.

I work behind the scenes

On your branding, your domains, your sender addresses. No fingerprints from me.

Clear scope before build

Fixed deliverables and boundaries, written down. No drift, no “while we’re at it.”

Screen walkthrough + documentation

Walkthrough video, support notes, runbook. Your team or another dev can take it forward.

No client poaching, no surprise upsells

I never reach out to your client outside of what we agreed.

Human review where needed

AI summaries, drafts, and notifications can route through a person before they go out when the workflow calls for it.

Engagement

Ways to work together.

Four shapes the work usually takes. Pick the closest match — we'll define exact scope, timeline, and budget together before any code gets written.

01

Fixed workflow build

One scoped workflow: intake, quote, document collection, follow-up, dashboard, CRM sync, or handoff.

Best when one painful process needs to work reliably.

02

Agency overflow implementation

You already sold the work. I help deliver the Make, AI, API, no-code, and backend pieces behind the scenes.

Best when you need capacity without hiring full-time.

03

No-code / AI / API bridge

Make, Bubble, Supabase, n8n, Zapier, Airtable, HubSpot, GHL, Twilio, Claude/OpenAI, or Sheets around API/webhook logic, state, and reliability.

Best when the chosen stack works, but the workflow needs stronger implementation.

04

Rescue and stabilization

Clean up fragile automations, unclear data flow, broken webhooks, duplicated records, missing logs, or unsupported handoffs.

Best when a workflow technically exists but is hard to trust.

Where I'm strongest

No-code where it fits. Custom code where it matters.

I'm no-code-friendly, not no-code-limited. I can work inside your Make, Bubble, Supabase, Airtable, HubSpot, GHL, n8n, or Zapier stack, wire in OpenAI/Claude where useful, and add custom API/backend pieces only when they make the workflow easier to support.

You don't need to know every tool here. Most projects use four or five of these, picked after we map the workflow.

Make.com
orchestration
Bubble
no-code app
Supabase
source of truth
Airtable
lightweight ops
HubSpot / Pipedrive / GHL
CRM layer
Twilio
SMS / voice
n8n
workflows
Zapier
glue
OpenAI / Claude
summaries / drafts
Human review
approval step
Webhooks
inbound events
REST / JSON APIs
integration layer
Queues / retries
reliability
Laravel
custom backend
PHP
runtime
MySQL / Postgres
datastore
Stripe
payments
Mailgun / Gmail
email
Google Sheets
ops log
Slack
notifications

Good fit / not a fit

Honest filter, before we talk.

I'm at my best when there's a real workflow to build. Left column — let's scope it. Right column — you'll get more leverage from someone else. Not sure which side you're on? Email anyway, I'll tell you straight.

Good fit

Likely a strong build.

  • You already have client demand but need technical delivery capacity.
  • Your agency wants to sell workflow automation, AI-assisted operations, CRM, or no-code implementation without hiring a full-time developer.
  • Your client workflow involves forms, emails, files, payments, AI summaries/drafts, notifications, dashboards, CRM updates, or handoff steps.
  • Make, Bubble, Supabase, n8n, Zapier, Airtable, HubSpot, or GHL is useful, but the workflow needs stronger state, reliability, API logic, or human review.
  • You want someone who can work white-label behind the scenes and hand off cleanly.
Not a fit

Probably not my best fit.

  • You’re still exploring ideas and there isn’t a specific workflow to build yet.
  • The project is mostly a brochure website, brand refresh, or cosmetic design work.
  • You need a pure Bubble/UI designer with heavy visual design focus.
  • The buyer, budget, or owner for the workflow is unclear.
  • You need unreviewed AI making final decisions on money, legal, safety, or customer commitments.
  • You need 24/7 managed support instead of a scoped implementation build.
Igor

About

Built by Igor.

I'm Igor, a Toronto-based workflow automation and API implementation developer. I work inside Make, Bubble, Supabase, Airtable, HubSpot, GHL, n8n, Zapier, and similar stacks when they fit, and add AI, custom API/backend pieces, dashboards, and reliability layers when the workflow needs more control or a real source of truth.

Toronto, CanadaEastern time No-code friendlyMake / Bubble / Supabase AI-assisted workflowsOpenAI / Claude / human review White-label friendlyBehind your offer

Availability & engagement

Practical details before you write.

Availability

Taking select engagements starting August 2026.

Eastern time · 10–20 implementation hours / week

Best first project

One scoped workflow, a small paid pilot, an automation rescue, or an overflow implementation block.

Fixed scope, written boundaries, clean handoff.

Pricing

Scoped, fixed-price builds. Budget discussed on the call.

Larger workflow, AI, API, or backend builds are scoped before kickoff.

Contact

Have a workflow that needs a technical layer?

Send me the messy version: what starts the workflow, which tools are involved, where data should live, what gets lost today, where AI might help, and what should happen next. A short note is enough — detail just helps me reply faster.

What happens after you send: I reply within 1 business day when possible from [email protected] with fit, questions, and a suggested next step. No sales call required to get a straight answer.


↑ Watch the proof videos

Is there already a paying client or internal buyer? (rough is fine)

Please don't send passwords, API keys, or private customer data. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.