One Small Team in Two Countries: Running Sales and Operations Across Singapore and Indonesia

A small interior fit-out firm has its director and designers in Singapore, its drafting and procurement team in Batam, and customers on both sides of the strait. A Singapore customer messages the director's phone at night. An Indonesian supplier chats with a buyer in Batam. A quotation in Singapore dollars is built from costs in rupiah on a spreadsheet only one person understands. When the director travels for a week, three things stall. The team is capable. It is run as two groups that happen to share an owner. A Singapore and Indonesia team works when it is built deliberately as one.

Decide who faces which customer

• One business number per market, published, answered by the team and not by an individual's phone.
• A named owner for each customer, and a named backup.
• Language by customer. Reply in the language they write in.
• Coverage hours stated for each market, including who handles which public holidays. The two countries share few of them.
• Handover rules between sales in one country and delivery in the other: what is promised, by whom, in writing.

A customer should never need to know which country the person answering sits in.

One record, both countries

The fastest way to split a team is to let each side keep its own notes.

• One customer list with the conversation history, notes, quotations and follow-up dates.
• One working language for internal notes, agreed by the team. English or Indonesian, whichever everyone reads comfortably.
• One place for files: drawings, quotations, supplier prices.
• One task list with owners and dates.
• Access by role, so people see what they need and sensitive financial information stays limited.

A working rhythm one hour apart

Singapore is one hour ahead of western Indonesia, so the day is almost shared.

• A fixed fifteen-minute call each morning at a time that suits both: today's priorities, anything blocked.
• A weekly review of the pipeline, deliveries and cash.
• Written handover at the end of the day for work that crosses the border.
• A shared calendar of public holidays in both countries, set up at the start of the year.
• In-person time every month or two. The ferry or a short flight is cheap compared with a misunderstanding.

Quoting in two currencies

• Quote each market in its own currency. Customers compare in the money they think in.
• Build prices from costs with an explicit exchange rate and a margin for movement. Write the rate and the date on the internal costing.
• State the validity period of a quotation. A rate that moves for two months changes your margin.
• For longer projects, agree how exchange movements are handled, or match the currency of your costs and your income where you can.
• Review rates monthly and update price lists deliberately, not by surprise.

Two currencies in the books

• Record each transaction in its own currency, with the rate on that date.
• Separate accounts for each bank account and each currency.
• One reporting currency for management reports.
• Exchange differences recorded as their own line, so they do not hide in margins.
• Intercompany dealings, if there are two entities, recorded on both sides and reconciled monthly.

A month-end routine that matches each bank account in each currency prevents most confusion.

Getting money across

• Know the cost of each transfer: the fee and the rate margin. Small frequent transfers are expensive.
• Batch payments to suppliers and staff where possible.
• Keep documents for every cross-border payment: invoice, contract, purpose. Banks and tax authorities ask.
• Pay people on time, in their currency. A salary delayed by a transfer problem is still a late salary.

Questions to take to an adviser first

Cross-border arrangements touch several areas of law in two countries, and the right structure depends on the facts. Before hiring or selling across the border, ask qualified advisers:

• Presence: does our activity in the other country require a local entity or registration?
• Employment: how can we lawfully engage people there, and which employment, social security and payroll obligations apply?
• Tax: where are profits taxed, and what applies to payments between the two countries, including withholding and indirect taxes such as GST and VAT?
• Invoicing: which entity invoices which customer, and what must an invoice contain in each country?
• Work permits and visas for anyone who travels to work in the other country.
• Personal data: which rules apply when customer and employee data moves between the two countries?
• Contracts: which law governs, and in which language must agreements be written to be enforceable?

Getting this right at the start costs far less than correcting it later. This article describes operating habits and is not legal or tax advice.

One culture, two contexts

• Make expectations explicit. Deadlines, quality standards and who decides should be written down.
• Invite disagreement. People in some working cultures hesitate to contradict a senior or a head office. Ask directly and thank those who speak up.
• Give credit across the border. The team that never meets the customer should hear the customer's praise.
• Equal respect for both offices. Avoid a head-office-and-back-office tone. Decisions, information and recognition flow both ways.
• Translate what matters: policies, safety rules and contracts, in a language each person fully understands.

When the director is the bottleneck

The opening story ends when three things are written down.

• Who can approve what: discounts up to a limit, purchases up to a limit, schedule changes.
• Who covers when someone is away.
• Where the information is, so nobody needs to ask the director's phone.

Common mistakes

• Customers contacting personal phones in each country.
• Two sets of customer notes.
• Costing spreadsheets one person understands.
• No explicit exchange rate in quotations.
• Mixing currencies in one bank account record.
• Hiring across the border informally without advice.
• Ignoring the other country's public holidays.
• Treating one office as the helper of the other.
• Every decision waiting for one person.

One workspace for both sides

A two-country team needs the same view of customers, tasks and money. Polynusa keeps customer conversations in a shared inbox on the business number with notes and follow-up dates, and includes bookkeeping and HR records in the same workspace. Check with your advisers how records for each country should be kept. See the pricing page.

Summary

A small team split between Singapore and Indonesia works when it is organised as one: a business number and a named owner per customer, one shared record in an agreed working language, a daily call and weekly review, quotations in each market's currency built on an explicit exchange rate, and books that keep each currency separate. Take questions about presence, employment, tax, invoicing and data to qualified advisers before hiring or selling across the border.

FAQ

Can a Singapore company simply hire staff in Indonesia?

Employment, tax and business presence rules apply in the country where people work, so this needs proper advice before anyone is hired. Common arrangements include setting up a local entity, working with a local partner company, or using an employer-of-record service. Which is appropriate depends on the activity and should be confirmed with qualified advisers in both countries.

How should a small business handle two currencies in its books?

Keep each transaction in the currency it happened in, and report in one home currency. Record the exchange rate used on the date of each transaction, keep bank accounts in each currency as separate accounts, and review exchange differences monthly. Decide which currency you quote in for each market and state it on every quotation.

Which language should a two-country team use with customers?

The customer's. Reply in the language the customer writes in, and keep internal notes in one agreed working language so that anyone on the team can pick up a conversation. Templates, price lists and policies should exist in both languages and be updated together.