Prompt Engineering for Philippine Business Users: How to Get Useful Outputs from AI Tools
The most common reason Philippine business users dismiss AI tools as "not useful" is not the tool — it is the prompt. A poorly constructed prompt produces generic, vague output that requires more work to edit than starting from scratch. A well-constructed prompt produces a first draft that is 70–80% complete and requires light editing.
The techniques that produce better outputs are consistent across tools — they apply equally to Microsoft Copilot, Google Gemini, ChatGPT, and Claude. This article covers the core techniques with examples relevant to Philippine business contexts.
The Fundamental Shift: From Asking to Briefing
Most poor prompts are questions. Most good prompts are briefs.
Asking: "Write a proposal for IT services."
Briefing: "Write a two-page service proposal for cloud migration services addressed to a 50-person manufacturing company in Laguna. The client runs on-premise servers with aging hardware. We are proposing Microsoft Azure foundation setup, Microsoft 365 deployment, and 12 months of managed services. Our differentiator is local support and a fixed monthly fee. Tone: professional but not overly formal. Include an executive summary, scope of work, and a next-steps section."
The brief gives the AI: the document type, the audience, the subject matter, the key points to include, the tone, and the structure. The output from the brief is usable. The output from the question is generic.
The Five Core Techniques
1. Specify the Role
Tell the AI what role it is playing. This is the single highest-leverage change most users can make.
Without role: "Write an email to a client about a delayed delivery."
With role: "You are a customer service manager at a Philippine IT distributor. Write a professional email to a corporate client explaining that their server shipment is delayed by 10 days due to DRAM supply constraints. Apologise, explain the cause briefly, and offer a timeline for the revised delivery. Keep it under 200 words."
Role specification gives the AI context about the voice, the expertise level, and the relationship. The outputs are measurably more appropriate.
Philippine business application examples:
- "You are a BIR-registered accountant in the Philippines reviewing a client's BAS..."
- "You are an HR manager at a Philippine SME drafting a memo about the new PhilHealth contribution schedule..."
- "You are a technical salesperson at a Philippine IT solutions company responding to a client's RFP for network infrastructure..."
2. Provide Context and Constraints
The more specific the context, the more specific the output. Constraints are as important as context — they tell the AI what not to do.
Context to provide:
- Who the audience is (technical or non-technical, executive or operational, external client or internal staff)
- What the document will be used for
- Any background information the AI needs to know
- Relevant Philippine-specific context (regulatory environment, local market conditions)
Constraints to specify:
- Word count or length ("under 300 words", "two paragraphs", "a one-page summary")
- Tone ("formal and professional", "direct and concise", "friendly but not casual")
- What to exclude ("do not include pricing", "do not use technical jargon", "avoid generic phrases like 'in today's fast-paced world'")
- Format ("use bullet points", "write in prose", "format as a table")
Example with constraints: "Write a follow-up email to a prospect who attended our webinar on Microsoft 365 for SMEs. They are a 20-person accounting firm in Metro Manila. Do not be pushy or use sales language. Keep it under 150 words. Offer a free 30-minute consultation. Do not mention pricing."
3. Show an Example
When you have a specific format or style in mind, showing an example is more efficient than describing it.
"Here is an example of how we write our service reports: [paste sample]. Write a service report in the same format for the following work: [describe the work]."
For Philippine businesses with established document formats — quotation covers, service reports, company correspondence — providing a sample and asking the AI to match the style produces output that fits the organisation's existing standards without extensive editing.
4. Iterate, Don't Restart
Most users write one prompt, get a mediocre output, and give up. The correct approach is to use the first output as a starting point and iterate.
"The third paragraph is too long. Shorten it to two sentences."
"Make the tone more formal throughout."
"Add a section on payment terms between the scope and the next steps."
"Replace the phrase 'leverage' with 'use' throughout."
Iterative refinement is faster than writing a perfect prompt on the first attempt. The AI retains context within a conversation — each instruction builds on what came before.
5. Use Philippine-Specific Context Explicitly
AI models have training data that skews heavily toward US and Western business contexts. When your output needs to be accurate for the Philippines — regulatory references, market conditions, local terminology — state it explicitly.
Without Philippine context: "What are the payroll deductions for an employee earning ₱25,000 per month?"
The AI may produce deductions based on US or generic figures.
With Philippine context: "Using current 2026 Philippine government contribution rates, calculate the SSS, PhilHealth, and Pag-IBIG deductions for an employee earning ₱25,000 per month. Also calculate the withholding tax using the TRAIN Law tax table. Show the computation."
Similarly for BIR forms, SEC filings, PhilHealth procedures, DTI requirements, and other Philippine-specific regulatory contexts — always specify "Philippines" and the specific regulation or requirement name.
Common Mistakes
Asking for "the best" without defining criteria. "What is the best UPS for our office?" produces a generic answer. "What UPS should a 10-person office in Cebu with three servers and regular brownouts buy? Budget is under ₱50,000. We need at least 30 minutes runtime." produces a specific, useful recommendation.
Accepting the first output without refinement. The first output is a draft. Treat it as one.
Not providing enough background. "Write a proposal" gives the AI almost nothing. The AI will write a generic proposal. The more background you provide, the more specific and useful the output.
Forgetting to verify factual claims. AI tools can produce incorrect regulatory figures, outdated pricing, and fabricated statistics. Any factual claim in an AI-generated document — especially BIR rates, SSS contribution tables, PhilHealth schedules — must be verified against the primary source before use.
A Practical Starting Template for Philippine Business Documents
For any business document — email, proposal, report, memo — this template structure produces consistently better outputs:
Role: [Who the AI is playing]
Audience: [Who will read this]
Task: [What to write, specifically]
Context: [Background information needed]
Format: [Structure, length, tone]
Constraints: [What to exclude or avoid]
Philippine context: [Relevant local regulations, market context, terminology]
You do not need to label each element. Writing them in natural language works:
"You are a project coordinator at a Philippine IT company. Write a status update email to the operations head of a BPO client in Ortigas. We completed the Microsoft 365 migration for 85 users this week. Three users have login issues we are resolving today. Training is scheduled next Monday. Keep it under 150 words. Formal tone."
That prompt — role, audience, task, context, format, tone — produces a first draft that requires minimal editing.
If your Philippine organisation is evaluating Microsoft 365 or Google Workspace deployment — the platforms that make tools like Copilot and Gemini available to your team — get in touch.
Talk to our Cloud & I.T. team →
