DANIEL KAM / WORKFLOW AUTOMATION

Doing the same task in too many tools?

Copying updates, preparing the same report or moving information by hand? I can help you turn one repeated task into a workflow you can test and understand.

Start with the task you want off your plate

I enjoy tinkering with tools and finding ways to make them useful in day-to-day work. We start with your current steps, decide what can be automated and keep people involved where judgement matters. A small pilot gives us something concrete to test before taking on a larger build.

What I can help you with

  • Map one task from the information it needs to the result you want.
  • Connect agreed tools through a small integration or AI pilot.
  • Test representative examples, errors and human review steps.
  • Explain how to run, check and pause the workflow, including its ongoing costs.

See my WordPress Block Catalog MCP, an open-source example of a focused integration.

Choose a starting point

These project budget guides are in SGD. Tell me what you need and I will confirm the work and fixed fee in a written proposal before you commit.

ProjectBudget guide · SGDIncluded scope
Workflow blueprintS$600One workflow mapped, with dependencies, risks and a written implementation scope.
One workflow pilotS$1,800Up to two agreed tools, one trigger, representative tests and operating instructions.
Production integrationScoped quoteDeployment, monitoring, security and reliability requirements assessed separately.

Paid tools, API usage and hosting are separate. A pilot tests a bounded use case; it does not imply production readiness or error-free AI output.

Your quote identifies any applicable taxes and third-party costs, so you can see the full payable total before accepting.

How we can work together

  • Tell me what is happening. Share the result you want, the current situation and anything you have already tried.
  • Agree on a piece of work. We confirm access, deliverables, exclusions, a fixed fee and how we will check completion.
  • Complete, review and hand over. I work through the agreed scope, explain the result and hand over the findings, files or instructions.

A few questions you might have

Does every automation need AI?

No. A straightforward rule or integration may be easier to run and check. We choose the approach around the task.

Can you connect my existing tools?

That depends on their integration options and your permissions. Those dependencies are checked before agreeing the build.

What happens when it fails?

We agree error handling and human review steps. Handover explains how to inspect failures and disable the workflow.

Tell me where you need a hand

You do not need a perfect brief. Start with the problem, what you have tried and what you would like to happen. These details will help:

  • What task repeats, and what should it produce?
  • Which tools does it move between?
  • How often does it run, and who uses the result?
  • Does it involve sensitive information? Describe categories only.
  • What needs human approval, and what should happen on failure?
  • What budget and target date should we work within?

Opens your email app. Prefer webmail? Write to [email protected]. Leave out passwords, API keys and customer records.