Who You'll Work With
A small team, which is deliberate. You deal with the people doing the work, not an account manager relaying messages.
Jerald Mark-Templin
Jerald builds the automation side of Smoothly: CRM systems in HubSpot, and the cross-tool workflows that connect them to everything else, on Zapier, Make, or n8n depending on what the job needs. He got here by being the person the manual work fell to — running a computer trading company, then property management, where a broken process isn't a diagram on a whiteboard. It's an order that never got placed and a call that never got returned.
He moved into CRM work in 2023, handling lead generation, data management, and pipeline building, and into automation itself in 2025. That order is the useful part: he spent two years watching where sales processes actually leak before he learned the tools that plug them. It is why an engagement starts with mapping how your business really runs rather than with a platform recommendation — the tool is the last decision, not the first.
Inside a CRM he designs workflows, sequences, and funnel architecture. Outside it, most of the skill is choosing correctly between platforms and then building so the choice holds up: Zapier when a workflow runs in a straight line and a non-technical team has to maintain it, Make when it branches or needs data reshaped mid-flight, n8n when it calls an AI step, needs custom code, or has to run self-hosted on your own server. Sometimes the answer is none of them — if the whole process already lives inside HubSpot, its own automation does the job and no middleware gets added.
Every workflow he ships has error handling on it, because an automation that fails quietly is worse than no automation at all — you carry on trusting a process that stopped working weeks ago. He builds the way he'd have wanted someone to build for him back when he was the one copying data between tabs late on a Sunday night: nothing hidden, nothing that only one person on the team understands, and everything written down before he hands it over. A system that only runs while he's watching it isn't finished — the point is that you stop thinking about it entirely.
Avegail Tongol
Avegail came to marketing through operations — administrative support, client outreach, and logistics coordination, where you see first-hand how a business actually attracts people and whether it keeps them. That order shaped how she works: marketing isn't a layer applied on top of a business, it's the part of the business a client experiences first.
She is HubSpot CRM trained in contact management, list organization, and pipeline follow-up, which means the campaign and the system underneath it get designed together rather than handed between people. Client communications, campaign support, and the internal process that keeps both organized are one job as far as she's concerned — because to the person on the other end, they are.
Her view is that good marketing isn't about making the loudest impression, it's about making the right one. The best systems are built around people, and the best marketing builds confidence long before anyone signs a contract.
Leenard Lacay
Lee didn't get into development because he wanted to write code. He was drawn to building things people actually use, and worked out early that software succeeds or fails on how naturally it fits someone's workflow — not on how many features it ships with.
He works across the whole stack in React, Next.js, TypeScript, and Node.js: interfaces, API integrations, business logic, performance, and the small details that decide whether something feels finished rather than merely working. Understanding the problem matters to him as much as implementing the solution, which is the same order the rest of our engagements run in.
What he cares about most is what happens after launch. Clean architecture and readable code are part of the product, not an afterthought — the real test is whether a system still makes sense months later to someone seeing it for the first time. Good engineering, in his view, is invisible: you shouldn't have to think about the technology, and nobody inheriting the work should have to fight it.