Selected work · Anonymized
Practical systems I’ve built.
These examples describe my contribution without naming clients or sharing confidential materials.
Sales prospecting and follow-up
From finding a potential client to a human sales conversation
I built sales agents that look for potential clients in databases the business already has access to, then start an automated cold-email sequence.
What I built
- Prospect discovery: identify potential clients in the databases available to the business.
- Initial contact: start the email outreach with an introductory message.
- Follow-up: in this project, send a second email 15 days later if there has been no reply.
- Final attempt: send a final email 15 days after the second, again only if the prospect has not responded.
- Sales handoff: when the prospect replies, the salesperson takes over to understand the need, continue the conversation, and sell or prepare a quote.
Available prospect databases → introductory email → follow-up after 15 days without a reply → final email after another 15 days → human sales conversation when a reply arrives.
The business value
The workflow connects prospecting, initial contact, and follow-up while keeping the salesperson responsible for the conversation once a lead engages. The three attempts and 15-day intervals describe this project’s setup; they are not a fixed approach for every business.
Customer service
Known-issue support with a route to an available person
I created a website containing the common issues already known in the business, giving the service agent a knowledge base to use when handling a customer’s request.
How the workflow works
- Known issues in one place: the website holds the business’s common support issues.
- First-contact support: the agent uses that information to try to resolve the customer’s issue at the first contact.
- Human escalation: if the agent cannot resolve the issue, the request is routed to an active human service representative.
Customer issue → known-issue knowledge base → attempted resolution → available human representative when needed.
The business value
Routine support has a defined starting point, and unresolved requests have a clear route to a person. The workflow aims for first-contact resolution without assuming every issue can be handled by an agent.
Consulting services
Client assessment and reporting workflow
I built an application that connects client questionnaire responses with results calculation and report preparation. The consultant receives the resulting material and takes charge of the next stage.
What I built
- Client intake: a form for the client to submit the information used in the assessment.
- Results processing: an AI-assisted step that calculates results from the submitted information.
- Report preparation: PDF documents containing the information to hand over.
- Consultant handoff: the consultant receives the material and continues the work with the client.
Client questionnaire → results calculation → report preparation → consultant handoff.
Where the consultant stays in charge
The application prepares information for the consultant. The professional takes responsibility for the client conversation and the work that follows.
12 years in business systems projects
My background includes configuring and automating business systems across manufacturing, retail, wholesale, nonprofits, and customer experience. That experience informs how I translate a business requirement into a practical workflow.
Illustrative applications · Not client case studies
Two more ways to make everyday work easier.
These are possible projects to explore together. They illustrate how the same approach can apply to other company workflows.
Client onboarding without the constant chasing
A new client is ready to start, but their information, documents, and internal tasks are spread across messages. A structured onboarding workflow can give everyone a clearer next step.
Confirmed client → intake form → internal task list → named owner → readiness check.
What I’d explore with you: one place to collect the required information, tasks assigned to the right people, reminders for missing items, and a shared view of what is ready or still waiting.
Where people stay involved: your team reviews exceptions, confirms the information is complete, and decides when the client is ready for the next stage.
A useful starting point if: each new client requires the same questions, reminders, or internal handoffs.
Weekly reporting that starts with a prepared summary
Someone copies updates from a CRM, spreadsheets, or project tools before every operations meeting. A reporting workflow can prepare the agreed information so the team can spend more of the discussion on decisions.
Agreed sources → scheduled collection → completeness checks → summary → owner review.
What I’d explore with you: which figures matter, where the correct records live, how to assemble the report, and who receives it. Missing or stale inputs should be flagged rather than filled with guesses.
Where people stay involved: the responsible owner checks unusual figures and adds the context behind the numbers. If AI helps draft a narrative, it should stay grounded in those records and be reviewed before sharing.
A useful starting point if: your team repeatedly builds the same report from the same sources.