If you are exploring AI agents for a small business in the Philippines, start with the work you want help finishing. Preparing a client call. Comparing supplier quotations. Turning scattered notes into a list of things that need your attention.
You do not need to begin with a plan to automate the whole business. Choose a piece of preparation that has a clear source, a useful result, and someone who can check it.
Here are practical examples to consider for a café, online shop, consultancy, or small service business. These are suggested tasks to test, not customer case studies or promises that every AI product supports them.
What are AI agents, in plain language?
An AI agent can work towards a task by choosing steps and using tools made available to it. Depending on the product and its permissions, that might involve finding information, working with a file, or preparing an output for review.
The label alone does not tell you what it can do. Before choosing a service, ask which sources it can use, which actions it supports, and where it must stop for approval.
Judge the result, not the label. A useful draft based on the right information matters more than a claim that a tool can handle everything.
Prepare a client briefing before a call
For a consultant or small agency, try asking for a briefing from the project notes and messages you choose to provide.
Keep the output focused:
- What the client last asked for.
- What has been completed since the previous discussion.
- Which questions remain unanswered.
- Which decisions you need during the call.
An example instruction:
Use these project notes to prepare a briefing for my client call. Separate confirmed facts from open questions. If a deadline is unclear, flag it. Do not invent a commitment or contact the client.
Read the briefing against the source material. The assistant should help you arrive prepared, not create a version of the project that sounds more settled than it is.
Turn an inquiry list into follow-up drafts
For an online shop or service business, start with a list of inquiries you have already collected. Include only the details needed for the task: what was requested, when you last replied, and the current status.
Ask for a draft follow-up for each inquiry you select. Supply the approved product details, availability, and terms rather than asking the assistant to guess them.
For example:
Prepare a short follow-up for these unanswered inquiries. Use only the information in this file. Do not offer discounts, promise delivery dates, or send anything. Flag inquiries where the next step is unclear.
If you want drafts in Filipino, English, or a mix of the two, request a sample and review the wording yourself. Do not assume the tone is suitable simply because it sounds fluent.
A follow-up should reflect what you can actually deliver.
Compare supplier quotations without hiding the gaps
Imagine a café reviewing packaging quotations from several suppliers. Give the assistant the quotations and specify the comparison you need.
Ask it to identify:
- The quoted item and quantity.
- Unit price and currency.
- Delivery charges and any stated taxes.
- Minimum order requirements.
- Payment terms and quoted lead time.
- Missing details that prevent a fair comparison.
Make the limits explicit: do not treat an omitted charge as zero, assume different pack sizes are equivalent, or describe the lowest quoted price as the best overall choice.
Check calculations against the original documents. The useful output is a clearer comparison and a list of questions to ask—not an automatic purchase decision.
Convert meeting notes into actions you can review
After a project discussion, provide your notes and ask for a draft action list.
For each item, request the action, the person responsible if named, the deadline if stated, and the note that supports it. Anything unclear should remain a question.
A suggestion such as “we could launch next month” must not become a confirmed launch deadline. An unnamed task should not quietly acquire an owner.
Review the list before sharing it. Organising a discussion is useful; rewriting what people agreed is not.
Check access before expecting execution
Mentioning your inbox, shop, or spreadsheet does not give an assistant access to it. Confirm whether the service supports the connection you need, or provide the relevant information through a supported upload or sharing method.
Before testing a task, establish:
- Which file or source should be used.
- Whether the information is current.
- What output you want back.
- What requires your approval.
- What should happen if information is missing.
Keep credentials out of ordinary chat and share only what the task needs. Start with preparation for your review before authorising changes to live records or messages to other people.
Choose the task whose output you can check
A sensible first test is a task you already understand. Use a real example, review the result, and note what needed correction.
Did it use the right source? Preserve the facts? Flag missing details? Give you something useful without making you rebuild the work?
If the answer is no, narrow the task before expanding it. If the result is useful and the work repeats, our guide to turning one weekly chore into a routine covers the next step.
With Rilke, start by describing the preparation you want help with and the limits you want respected. Explore how Rilke works, then test one task against your own standard.
You do not need an agent that claims to run your business. You need help with work you can clearly explain and confidently review.