Keep the rehearsal at the desk.
A founder wants to move abroad while continuing to run a small Bitcoin-accepting consultancy. The formation provider can explain how to establish a new entity. The founder can operate the payment software from a laptop. Neither fact shows whether the business can handle its ordinary obligations after the proposed move. A structured rehearsal can reveal the missing pieces before money is spent on implementation.
Run the exercise at a desk using fictional invoices, synthetic customer information, and descriptions of existing processes. Participants work through what they would do and which evidence or authority they would need. If a software check is useful, use an isolated test environment with test credentials and no real funds. The exercise maps the proposed operation; actual travel, work abroad, filings, and payment changes remain separate implementation decisions.
Choose a realistic future month and describe the proposed arrangement. Where would the founder live? Which company would contract with customers? Who would issue invoices, maintain records, receive official correspondence, make employment decisions, and approve payments? Where would each person perform those activities? Write unknowns as unknowns. The rehearsal must not quietly treat a proposed permission as already obtained.
In our fictional example, the business has six staff, customers in several countries, a fiat operating account, and a Bitcoin payment option. The founder is considering a move for family reasons. The current company may continue, but a second entity has also been suggested. The purpose of the exercise is to identify what either option would need, not to make a new entity appear inevitable.
Assign an exercise coordinator who can interrupt the scenario and record dependencies. The founder should participate but should not answer every question on behalf of payroll, the accountant, or a local professional. A confident guess can make a rehearsal look smooth while hiding the very uncertainty it was meant to find.
Finish the setup by defining the output: an event log, a list of unresolved permissions, a responsibility map, and a small number of decisions. The result is a planning asset. It is not a legal opinion, proof of immigration eligibility, or evidence that a company has actually relocated.
Build the month from obligations the business already has.
Use the previous quarter to identify recurring events without copying unnecessary personal data. Include customer onboarding, a late payment, an invoice correction, a refund request, supplier bills, payroll approval, official correspondence, and a request from an accountant. Add one event that normally reaches only the founder, such as an insurer’s question or an unusual contract amendment.
Give each event a trigger, a deadline, and a definition of completion. A customer asking for an invoice triggers a different process from a payment appearing in a wallet. A refund request is not complete when a support agent says yes. It may require a commercial decision, verification, approval, execution, and accounting. The scenario should follow the event through the last relevant handoff.
Bitcoin payment software provides a useful illustration. BTCPay Server’s current invoice documentation distinguishes payment and settlement states and describes exceptions such as partial or late payment. It also explains that a manual status change does not itself prove blockchain confirmation. In the rehearsal, ask who interprets the actual state and who decides what the customer should receive. Do not turn a dashboard color into a universal fulfillment rule.
Give the accountant a realistic request: explain how a fictional invoice, payment, fee, and refund appear in the records. A transaction reference alone will not identify the contract, business purpose, or approved treatment. The exercise should test whether the relevant documents can be brought together without asking the founder to reconstruct the story from memory.
For a British company, official guidance describes both company records and accounting records, including money received and spent, assets, debts, and supporting documents. That is a concrete example of why operating records cannot disappear when a founder moves. The actual recordkeeping and retention rules for another entity must be checked in its own jurisdiction.
Include quiet days. An exercise containing only crises can miss routine friction such as a letter that waits in a mailbox or a supplier question sent after the responsible person’s working hours. The ordinary operating rhythm often determines whether the proposed arrangement will remain affordable after the enthusiasm of the move fades.
Run four weeks with a different question each week.
In the first week, ask whether information reaches the right person. Present a fictional new customer, a supplier invoice, and a piece of official mail. Nobody should need an unexplained personal inbox or a private phone message to find the responsible owner. Record the route the information takes and whether it arrives with enough context to act.
In the second week, ask whether the decision can be made. Introduce a partial Bitcoin payment, a request to change invoice details, and a payroll adjustment. Require participants to identify the commercial or professional decision before discussing the software button. If nobody knows who has authority, record that failure rather than allowing the founder to resolve it informally.
In the third week, test interruption. Make the founder unavailable in the fictional scenario, delay a provider response, and send an advisor a request that crosses two jurisdictions. The objective is not to demonstrate heroic improvisation. It is to identify a lawful pause, a documented escalation, or an alternate person with the necessary authority and access.
In the fourth week, ask whether the records explain the month. Give a reviewer the event log and supporting fictional documents. Ask them to trace an ordinary sale, an exception, and a payment decision. Then ask which unresolved permission could prevent the proposed future arrangement from being used at all. A technically successful month can still fail the professional review.
The schedule below models 30 days of business activity. You can work through it in a few short tabletop sessions rather than wait a real month. Preserve the sequence, deadlines, and intended working hours so the compressed exercise still exposes delays and dependencies. Reserve a final session for corrections and review, and keep fictional events clearly labeled so they do not enter live customer or accounting records.
| Period | Fictional event | Evidence expected | Question left for review |
|---|---|---|---|
| Days 1 to 3 | New customer and contract request | Contracting entity and authorized signatory identified | Can that entity lawfully provide the actual service? |
| Days 4 to 7 | Supplier invoice and official letter | Named recipient, due date, escalation route | Who must receive or act on formal correspondence? |
| Days 8 to 11 | Partial Bitcoin payment | Invoice state, customer response, accounting note | What commercial policy applies to the shortfall? |
| Days 12 to 15 | Payroll adjustment and staff request | Decision owner and advisor referral | Which employment and payroll rules need review? |
| Days 16 to 20 | Founder unavailable and provider delayed | Approved alternate or documented pause | Which decisions cannot be delegated as proposed? |
| Days 21 to 25 | Refund and accountant request | Approval, fictional payment trail, reconciled records | Which tax or contractual treatment remains unresolved? |
| Days 26 to 30 | Independent month-end review | Open issues, owners, dependencies, decision record | What must be resolved before any real relocation? |
Separate an operating defect from a permission problem.
The event log will produce different kinds of findings. A missing invoice reference is an operating defect. A staff member unable to view a required report is an access question. Uncertainty about who may bind the company is an authority question. Uncertainty about whether the founder may perform the proposed work in the destination is an immigration question. Each needs a different owner.
Use this distinction to avoid buying the wrong solution. A new company does not repair an undocumented refund procedure. A better payment integration does not settle employment permission. A registered-office service does not necessarily make business decisions or supply every required local function. Write the defect in terms of the failed task before considering a product or jurisdiction.
For professional review, preserve the proposed facts rather than a preferred conclusion. Explain where decisions would be made, who would perform work, which customers would be served, how contracts would be signed, and how money would move. Qualified advisors can assess tax, corporate, employment, immigration, and other applicable issues against those facts. The exercise should not label every foreign activity harmless or assume every activity creates the same exposure.
Compare alternatives against the same events. If the current company remains, what changes? If a second company is added, which new contracts, records, accounts, and responsibilities appear? If the founder delays the move, which problems still deserve correction? Repeating the same month makes the additional work visible without pretending that every option has an identical legal result.
Include cost and capacity. Record the staff time required to prepare a complete payment request, the provider response time, and the number of professional handoffs. Use the team’s observed rehearsal time as an internal estimate, clearly distinguished from a provider quote or government fee. An arrangement that is technically possible may still be too demanding for the people who must run it.
Some findings should stop the proposed implementation until reviewed. Others can be fixed in the current business immediately under its normal authority. Keep those categories distinct. A useful plan does not freeze routine improvements while waiting for a country decision, and it does not treat small operational progress as approval for the whole move.
Turn the result into a sequence with named owners.
At the end of the month, produce a short decision record. Describe the business arrangement tested, the events that passed, the events that failed, and the assumptions that remain unverified. Attach the fictional evidence and the version of the process used. A future reviewer should be able to understand the exercise without attending every meeting.
For each unresolved point, specify the next action and the expected evidence of completion. An immigration question may need a written route assessment or an authority decision. A payroll question may need advice followed by a configured process. A wallet question may need a separately authorized technical test. Avoid closing an issue merely because an email has been sent to a professional.
Order the real steps by dependency. There may be little value in paying for a new company before establishing whether the intended personal move is workable. There may be no reason to replace an existing payment system if its only defect is a missing reference field. The rehearsal should help the founder spend on decisions that are ready to be made.
Run a shorter second exercise after the material issues have been addressed. Use a different fictional customer and a different exception so that participants must understand the process rather than memorize the first answer. Confirm that the improvements still work when the founder is not the person explaining every step.
The eventual relocation decision can then be made with a clearer view of the operating burden. Some founders will proceed with the original structure. Others will change the timing, narrow the move, or obtain a different professional design. Any of those can be a useful result if it follows the household’s needs and the business facts.
Keep the boundary visible throughout: the tabletop is preparation. Actual work abroad, changes to corporate arrangements, payments, filings, and provider instructions require their own authority and implementation. The rehearsal earns its value by making those next steps concrete, not by quietly performing them.
The whole picture
The Bitcoin Lawyer take
Give the rehearsal a difficult Tuesday. Identify who can sign if a customer needs a refund while the founder is traveling or the bookkeeper is asleep.
Change the plan where the rehearsal exposes a genuine obstacle. That might mean a different authorization, confirmed permission to work, or postponing the move.


