Work

Sales Development Representative, Talstack (current)

As part of my current SDR role, I've built the systems that scale and route outbound prospecting, rather than just running it manually. Specific internal tools and platforms aren't detailed here.

Challenge

Manual outbound (cold calls, emails, LinkedIn outreach) has a ceiling on volume, and qualified leads need to reach the right rep quickly to avoid stalling in handover.

What I built

• An AI calling system to support outbound prospecting
• A lead routing system through the CRM that gets qualified leads to the right rep automatically
• AI-automated outreach sequences to extend prospecting beyond manual capacity
• Lead magnets to support inbound lead generation alongside outbound

My role

I designed and built these systems within Talstack's existing sales workflow, working alongside the sales team to fit them to how leads are actually qualified and handed off.

Technology

n8n for workflow automation, LLM-powered logic for the AI calling and outreach, connected to the company's CRM for lead routing.

Outcome

This work is ongoing as part of my current role.

Real estate industry, 3 businesses, implemented through referral

Three real estate businesses, each referred by the previous, hired me to replace manual customer and payment processes with a connected digital system. Rather than three unrelated engagements, this became one repeatable Zoho operations system, adapted to each business's specific requirements.

Challenge

Each business was managing a large customer base through manual processes: screenshots, paper forms, and disconnected records. This made it difficult to track customer information, follow up on installment payments, generate invoices and receipts, communicate with customers, manage enquiries, and handle legal documentation reliably.

Solution

I designed and implemented a connected Zoho operations system built around one core workflow. A customer subscribes through a Zoho Form, providing the required information. That information flows into Zoho CRM, where the team manages the customer and their transaction. When a payment is made, the team verifies it in the system; once confirmed, the customer receives an invoice and a receipt, and the transaction is recorded against their record. For installment payments, customers submit a follow-up form indicating what they've paid, which the accounting team verifies before the appropriate invoice and receipt are generated.

What I built

This wasn't a single CRM setup. I connected multiple parts of the Zoho ecosystem into one workflow:

• Zoho CRM for customer and business process management
• Zoho Forms for customer information and payment submissions
• Zoho Books for invoices, receipts, and payment records
• Zoho Campaigns for customer communications, including promotional and celebration emails
• Zoho Sign for legal documents requiring customer signatures, such as deeds of assignment
• Zoho Desk for handling customer enquiries and support

The work was in the integration between these systems: customer submission flowing into CRM, payment verification flowing into accounting, and accounting flowing into invoicing, receipts, and communication, not just configuring each product in isolation.

My role

I handled solution design, configuration, implementation, and the automation connecting each system, adapting the core workflow to each business's specific requirements across all three engagements. For one of the three, I also managed the company's email infrastructure: business email setup, DNS configuration, and ongoing technical administration.

Technology

Zoho CRM, Zoho Forms, Zoho Books, Zoho Campaigns, Zoho Sign, Zoho Desk.

Outcome

Replaced manual, screenshot- and paper-based tracking with a connected digital workflow covering customer intake, payment verification, invoicing, receipts, communication, and legal documentation, reducing the manual work involved in each step.

Back End Developer, Side Hustle

Business problem

myStudyPadi needed a working backend to actually run the product for its early users, and the company needed a public site that could grow inbound traffic and attract more of them.

System

Built the backend that powered the app end to end, and separately built and launched a WordPress blog for the company's public site to drive organic traffic.

Technical implementation

Node.js/Express REST API backend with MongoDB and JWT-based authentication. WordPress site with custom plugins and themes for the blog.

Impact

The backend supported 500+ registered users on myStudyPadi, with a 30% improvement in server efficiency and a 50% reduction in response time. The WordPress blog grew site traffic by over 40% within three months.