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.
OpenAI Select Partner
Read the announcement
Agencies and consultancies: I also work white-label behind your brand.
Apps I've built
Two of them are the systems behind the proof videos above — real codebases, running live. The third is an earlier product with paying users.
Multi-tenant intake SaaS for electricians. Token-link request pages, file uploads, private operator inbox, SMS/email notifications, appointment reminders, request timelines.
Multi-tenant Laravel platform for prospect mining, personalized demo sites, private proposal pages, Stripe checkout, onboarding, lead capture, and operator review.
Earlier Laravel SaaS, different audience. Shows the platform-shipping pattern at scale.
Proof — 04 walkthroughs
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.
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.
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.
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.
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.
What I build
Six things I get asked to build most. Pick one. Scope it. Ship it.
Structured forms, file uploads, private customer pages, owner/admin inboxes, and status timelines.
Operator and client dashboards for portals, support teams, admins, fulfillment workflows, and handoff steps.
OpenAI/Claude summaries, draft replies, classifications, reminders, human review steps, and safe notification loops.
API glue around Make, n8n, Zapier, HubSpot, GHL, Pipedrive, Airtable, Sheets, Stripe, Twilio, and client systems.
No-login upload flows, missing-info requests, onboarding checklists, file review screens, and AI-ready summaries.
Queues, retries, event logs, operator visibility, documentation, and screen walkthroughs.
How it works
Fixed scope. Existing stack respected. Documented handoff. You stay client-facing, I stay implementation-facing.
We define the one workflow that matters: intake, quote, onboarding, follow-up, document collection, dashboard, or internal handoff.
Clear deliverables, boundaries, tools, data flow, and handoff expectations — written down before code.
I build inside the chosen stack — Make, n8n, Zapier, Bubble, Supabase, HubSpot, GHL, Airtable, or custom API/backend pieces where useful.
Working system, screen walkthrough, support notes, and a clean handoff so your agency keeps the client relationship.
White-label 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.
Your client knows your agency, not me — unless you introduce me.
On your branding, your domains, your sender addresses. No fingerprints from me.
Fixed deliverables and boundaries, written down. No drift, no “while we’re at it.”
Walkthrough video, support notes, runbook. Your team or another dev can take it forward.
I never reach out to your client outside of what we agreed.
AI summaries, drafts, and notifications can route through a person before they go out when the workflow calls for it.
Engagement
Four shapes the work usually takes. Pick the closest match — we'll define exact scope, timeline, and budget together before any code gets written.
One scoped workflow: intake, quote, document collection, follow-up, dashboard, CRM sync, or handoff.
Best when one painful process needs to work reliably.
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.
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.
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
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.
Good fit / not a fit
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.
About
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.
Availability & engagement
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
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.