Which accounts deserve attention today?
Bringing account signals and relationship history together to support a clear next action.
Real build · Fictional walkthrough
I help lean B2B teams fix how work moves through sales, operations and finance: clearer priorities, follow-up that happens, handoffs with a named owner, and payments that reconcile on their own.

Tre is Vietnamese for bamboo. It is strong because it grows in segments, and every joint is a place where it can hold or crack. Tide is the work moving through your business. My job is the joints: the handoffs between people, tools and teams.
Since 2024 I have built systems for 8 B2B teams across the US, UK and APAC: account signals and scoring, CRM clean-ups, sales-to-customer-success handoffs, payments and invoicing, and a full operations platform for a podcast studio. I spent 18 months coaching Clay cohorts at Bootprint (formerly Clay Bootcamp). I am the first n8n Ambassador in Vietnam, and I am part of the Attio Creator Program, so I know the CRM side as well as the automation.
Before automation, I spent nearly three years as a project manager at Fame, and I worked in onboarding, KYC and fraud operations at Kraken, so I know how careful money and identity work has to be. I build for the people who run the system every day, not just for the demo.
I would rather show a system working than talk about it. So I build live in front of the room, demo how Claude Code writes n8n workflows, explain how a signal turns into a conversation, and answer the questions people are too polite to ask in the chat.
Podcast guest · Leveraging AI, episode 218
Zero to Leads: how to build a personalized LinkedIn outreach machine for your ICP
A live session with host Isar Meitis: how I find, enrich and reach the right people, step by step.
Listen (opens the episode in a new tab)
I start by finding where your data actually lives, and where it stops moving.
Each one was added for a single need. Nothing connects, every change breaks something, and nothing learns from what already happened. You need one system that lasts, and gets better as your team uses it.
The CRM, the ad platforms, analytics, spreadsheets, inboxes, Slack threads and someone's notes. When it is time to act, nobody can see all of it.
Reports disagree, and dashboards show what happened but not what it means: which account to call today, which campaign to stop, what to fix first.
A login expires or a tool changes how it connects, and data stops flowing. The report still loads, so nobody notices until a customer asks where their invoice is.
Marketing passes a lead to sales, sales passes a customer to operations, and each step loses a little context.
For a small team, every booking means an invoice to make, a payment to chase and a record to update in the books. That should run smoothly on its own, from the booking to the paid invoice in your accounting.
The same four steps every time. The build itself takes one focused week.
Before I touch a tool, I ask about the outcome you want, who runs the work, and the one example that keeps going wrong.
You show me how it runs today. We take it apart together, step by step, and agree what to build.
I build everything we agreed in one focused week, and test it on real examples, including the awkward ones. Anything that touches money runs in test mode first.
You get written SOPs and hands-on training, so your team runs it and can change it without me.
Three short cases. Each explains one decision and lets you try a small, fictional version of it.
A walkthrough of one system I built for a small recording studio, from the first booking to the paid invoice in the books. Example data only, no live accounts.
More use-case videos are on the way.
Bringing account signals and relationship history together to support a clear next action.
Real build · Fictional walkthrough
Teaching the decisions behind a useful automation, through a small worked example.
Coaching · Illustrative exercise
Turning customer feedback and website observations into practical recommendations.
Independent prototype · Fictional example
Each of these runs, or has run, for a real team. Team names stay private.
See everything I have builtWhich accounts need attention today, and why: signals, scoring and a short daily list for each rep.
Built A production signals engine for a B2B sales team, with one Slack message per rep each morning.
Clean records and one owner per deal in HubSpot or Attio, and handoffs from sales to onboarding with nothing retyped.
Built A closed-won handoff for a B2B sales team, with an approval step in Slack before onboarding starts.
Workflows that move data between your tools, with error alerts instead of silent failures.
Built A meeting pipeline moved from Zapier to n8n.
Checkout, invoices and reconciliation in Stripe or QuickBooks, with card or bank payment and an alert when a payment fails.
Built Booking to paid invoice in QuickBooks for a podcast studio, and membership billing in Stripe for a coaching business.
When spreadsheets stop coping: one connected system for bookings, records, payments and updates, with a small app where you need it.
Built An operations platform for a podcast studio: booking portal, iOS app, staff admin and Slack updates.
Summaries, research and drafts that save time, checked by rules and approved by people.
Built Account signals that draft an email only after the rep picks who to write to.
Not sure which one fits you? Book a call and we will work it out together.
B2B sales, GTM and operations teams, from sales teams to studios and membership businesses. I design or improve the system so every lead, deal, booking and payment has one record and one owner.
Usually account signals, CRM clean-ups, handoffs, bookings and billing.
Book a call (opens Google Calendar in a new tab)Scoped builds in Clay, n8n and the CRMs you work in, set up so you can reuse them across accounts, and delivered with SOPs your team can maintain.
A good fit for GTM and automation agencies, and owners turning their agency into a system.
Book a call (opens Google Calendar in a new tab)Every project starts with a written scope and an estimate you agree to before any work begins.
For teams that have outgrown spreadsheets. I map how the work runs from end to end, then design and build one system around it: CRM, bookings, payments, a small app where it helps, and Slack updates.
Example An operations platform for a podcast studio, from the first booking to the paid invoice.
Your tools are in place, but they do not work together. I review them with your team, collect feedback, and then build and ship the fixes myself, round by round. You get changes that are live, not a list of suggestions.
Example Account signals and sales handoffs for a B2B sales team, improved one feedback round at a time.
Written SOPs and hands-on training, so your team can run the system and change it. Also available on its own, for anyone learning to build.
Example Clay and n8n coaching through real builds, plus SOPs, a walkthrough and an ownership checklist for every system I hand over.
Ready to build a system that lasts, or improve the one you run? Tell me what your team runs on today and what you want it to do. We will work out together whether to build something new or improve what you have.
Something else on your mind? Ask me directly.
Book a call (opens Google Calendar in a new tab)I design, build and improve the systems a team runs on: CRM, automations, bookings, payments and reporting, connected to the tools you already use. Then I hand them over with SOPs and training. I work with B2B sales, GTM and operations teams, and with agencies that need a builder behind their strategy. Since 2024 that has included 8 B2B teams across the US, UK and APAC.
A 1-hour consultation is $50 (USD). Project work is $40 (USD) an hour, and every project starts with a written scope and an estimate you agree to first. Running costs are usually low: I build on tools like GitHub Actions, Cloudflare and Trigger.dev, or n8n where it fits, and the code and workflows live in your own accounts, so you own them.
Usually, yes. I start with what you have: HubSpot or Attio, Google Workspace, Slack, ClickUp, n8n, Zapier or Clay, and QuickBooks, Xero or Stripe for finance. If a tool is causing the problem, I will say so and explain the trade-off.
Carefully. Payment work runs in test mode first, with a check before anything goes live and your yes for each live step. Charges and emails are built so a retry never bills anyone twice, every step is logged, and keys stay in your own accounts, never in documents.
You get SOPs, a walkthrough and an ownership checklist, and we train together until your team can run and change the system without me. Each build sends an alert when a step fails, and the SOPs say what to check first. If you want me on call after the handover, we agree that separately. Training can also be booked on its own: I spent 18 months coaching Clay cohorts at Bootprint, and I am the first n8n Ambassador in Vietnam.
Da Nang, Vietnam (GMT+7), working remotely. I overlap with APAC and the UK during the day, and with the US through early-morning or evening calls and async updates in Slack.
A practical guide for the meeting that decides what to improve next: a four-step prep method, questions for four meeting types, a one-page brief and a prompt for drafting it.
The questions I ask before I touch a tool, and what each answer changes in the build.
How a podcast studio's booking portal, payments, iOS app and Slack updates were built to work as one. No names.
Coming soon
One small build, step by step, with the choices I make along the way.
Each post grows out of one of my LinkedIn posts. See the blog
Tell me what your team runs on today and what you want it to do. We will work out together whether to build something new or improve what you have.
I usually reply within a day.
Have a question? Leave me a message.
Book a call or find me on LinkedIn.
Sent. I'll reply by email within a day.
That didn't send. Please book a call or message me on LinkedIn instead.