An overseas prospect may understand what a bookkeeper does but still have questions about working with you. Where are you based? What work do you handle? How will you communicate? What happens after the first inquiry?
Your website should answer those questions without pretending that your business is somewhere else. A Filipino bookkeeper can present a remote service clearly and professionally while being honest about location, experience, and availability.
The ideas below focus on the public website. They do not turn it into a client portal or replace the systems you use to manage an engagement.
Lead with the service, then explain the working arrangement
A homepage needs a clear starting point. Tell visitors the kind of business you help and the support you actually provide.
A fictional introduction might read: “Remote bookkeeping support for small service businesses.” The following paragraph could explain that the practice is based in the Philippines and works with clients through agreed online communication.
Your own wording should reflect your actual experience. Do not claim an industry specialism, software credential, or overseas office just because a competitor includes it.
The aim is to help a visitor recognize a fit before they contact you. A long list of countries is less useful than a clear explanation of the work and how the relationship operates.
Make communication expectations visible
Time differences are a practical consideration for a remote service. Explain the hours or overlap you can genuinely maintain, and make the time zone clear when publishing availability.
Do not advertise 24-hour support if you cannot provide it. A realistic expectation is easier to maintain and gives prospects a more accurate picture of the service.
Explain which channel you use for first inquiries. You can discuss the working communication arrangement during onboarding rather than publishing every internal tool and procedure on the homepage.
If meetings require an agreed appointment, say so. Visitors should not assume that sending a message guarantees an immediate live call.
Show relevant experience without exposing client records
Your About page can explain the businesses you have supported and the work you are equipped to do. Keep the wording specific and accurate.
If you mention software experience, describe your real level of familiarity. A public logo or badge should only be used when you are entitled to display it.
Never use a screenshot of a client's records simply to make the website look credible. If you need a visual example, create a clearly labelled demonstration using fictional information that cannot be mistaken for a real client result.
Testimonials and case studies also need permission. Preserve approved wording and avoid adding claims the client never made.
Explain the service boundaries
An overseas prospect may use familiar terms differently from another client. Your Services page should describe the actual tasks and how the scope is agreed.
Be clear about work that needs another professional or separate arrangement. Do not imply that bookkeeping support automatically includes tax advice, statutory reporting, or other work outside your qualifications and engagement.
Avoid writing jurisdiction-specific guidance unless the appropriate professional has reviewed it and you can keep it current. The website can explain your service without becoming a substitute for professional advice.
A helpful service description identifies the client, the kind of support, and the next question to discuss. It does not need to promise a solution to every business situation.
Use a short process section
A simple process helps prospects understand what happens after they contact you. Base it on your actual workflow.
| Stage | What the public website can explain |
|---|---|
| Inquiry | The information needed to start a conversation |
| Discussion | How you assess whether the support is suitable |
| Scope | How responsibilities and terms are agreed |
| Onboarding | That private access and documents follow an agreed process |
The public explanation should stay at this level. Detailed access instructions and document requests belong in the appropriate private workflow after the relationship is established.
Keep the inquiry form focused
Ask for a name, reply email, short business description, and the support needed. If the market served is relevant to assessing fit, ask for a broad business location without collecting unnecessary personal information.
Add a clear instruction not to submit financial records or account credentials through the general message field. The first form should help you reply, not become an unplanned document storage system.
Explain what happens after submission. A plain confirmation that the message was received is better than a vague success screen with no next step.
Before launch, test the process using agreed sample information. Confirm the destination inbox and who is responsible for checking it.
Give returning clients a separate route
If you already use a portal or document service, label its link clearly. New prospects should not have to guess whether a login is required before they can inquire.
A website link to a tool is different from building or embedding that tool. Tell the developer which arrangement you need, and keep third-party subscriptions visible in the scope.
Do not assume that a small public website package includes private accounts, permissions, or client dashboards. Those features need separate planning.
Plan a useful four-page website
A focused first version can use Home, About, Services, and Contact. Each page should answer a different question.
Home introduces the audience and support. About explains who does the work. Services clarifies the scope and boundaries. Contact explains how to inquire and what happens next.
You can include communication details in the relevant sections rather than creating a separate page for every working arrangement. Add pages when they provide distinct information, not just a longer menu.
My developer hiring questions can help you prepare the brief and compare proposals.
Think about language and tone
Plain English is usually more useful than phrases chosen to sound corporate. A prospect should understand the offer without translating a paragraph of business jargon.
Use the words you would use during a clear first conversation. Explain unfamiliar terms when they matter, and remove sentences that repeat the same promise without adding detail.
Check the writing from the reader's point of view. Can they identify the service, the person behind it, and the next step? If not, simplify the introduction before adding more sections.
Check the mobile experience
Prospects may open a referral link on a phone. Test the page in that setting before launch.
Read the service descriptions, open the menu, and find the inquiry route. Check that text remains readable and buttons are comfortable to use. If a table is included, confirm it does not become a confusing sideways scroll.
Motion should not delay access to information. Avoid animated figures that look like measured client results when they are only decorative examples.
My pre-launch checklist covers additional checks for a small business website.
Choose a build that fits your content habits
Every website I build is scoped and priced around what your business actually needs, so there's no one-size-fits-all package. Tell me about your pages, goals, and timeline, and I'll reply with a fixed written quote. Get a quote or send me your requirements.
Make the real working relationship easy to understand
You do not need to hide being based in the Philippines or suggest that you can do every kind of accounting work. You need a clear explanation of your actual service, experience, and process.
Online checkout, booking systems, member logins, business email setup, and self-editing all add scope. Put any of those requirements in your brief so the quote includes the work you expect.
