Optional cookies require your permission.Privacy & cookies

Can your Bitcoin business run for two weeks without you?

A customer needs a refund while the founder is away. The support team can identify the invoice, but someone still needs authority to approve the payment.

Adam Juchniewicz, CEO, Bitcoin Lawyer10 min read
Sources cited in this essay (3)
A customer-support operator wearing a headset works at a monitor in an office.
In this essay6 sections
  1. Define what must continue and what can wait.
  2. Separate seeing, operating, approving, and signing.
  3. Give exceptions an owner and a stopping point.
  4. Rehearse the fortnight without putting the treasury at risk.
  5. Make the return as orderly as the departure.
  6. The Bitcoin Lawyer take

Define what must continue and what can wait.

A founder wants two weeks away from a small online business. The company accepts Bitcoin, delivers digital training, and uses several outside providers. Staff can answer most customer questions, but payment exceptions tend to reach the founder. The accountant asks the founder for missing references. The hosting provider sends important notices to an address only the founder checks. The holiday reveals an operating problem that has existed for months.

This is an ordinary, planned absence by a living founder who remains capable of making decisions. It is not an inheritance plan, a response to incapacity, or a proposal to transfer ownership. Those situations require different legal and practical arrangements. The immediate task is to keep routine operations working for a defined period while preserving appropriate control over exceptional decisions.

List the business promises that fall within the fortnight. Include customer delivery, support response times, supplier payments, payroll, refunds, reporting, official correspondence, and technical maintenance. Mark the tasks that genuinely require a decision during that period. Avoid treating every possible improvement as urgent simply because the founder is leaving.

Then list what can pause. A new treasury design, a discretionary provider migration, a large unusual purchase, or a new country launch may be better deferred. The company should decide that deliberately and communicate it to staff. Otherwise someone may interpret the founder’s absence as permission to improvise, while another person refuses a routine task that was already within their role.

Set the intended level of contact. Perhaps the founder is unavailable for ordinary questions but can receive a genuinely exceptional escalation through one channel. Perhaps an authorized alternate can handle all planned decisions. Either can be workable. What fails is telling everyone the founder is offline while privately expecting the founder to approve every payment from a phone.

A good absence plan is therefore a service plan for the company. It identifies what customers and colleagues can expect, which people will deliver it, and what happens when an event falls outside the agreed boundary. It should make the fortnight less dependent on personal favors, not simply hide those favors behind a holiday message.

Separate seeing, operating, approving, and signing.

Start with tasks before software permissions. A support colleague may need to see whether an invoice was paid. An operations colleague may need to create an invoice or prepare a refund request. A manager may approve the commercial remedy. A treasury signer may execute the payment. These roles can overlap in a small company, but the overlap should be deliberate and visible.

The four functions are not interchangeable. Being able to view a payment does not authorize a refund. Being able to prepare a transaction does not establish the business reason for sending it. Holding a signing key does not automatically grant authority under the company’s documents. Ask the responsible corporate professional about any proposed delegation that changes who may make company decisions.

BTCPay Server offers a concrete technical example. Its API documentation distinguishes permissions and allows store-scoped access. The documentation advises requesting the narrowest useful permissions and warns that an omitted permission list can produce unrestricted access. That supports a careful design, but it does not certify the roles configured in a particular company’s server. The technical owner must check the installed version and actual accounts.

Review integrations as well as human users. A shop plugin, reporting script, or customer-support tool may have a credential created long ago with broader access than it now needs. The founder’s absence is not the moment to make untested production changes, but it is a reason to identify those dependencies and schedule a controlled correction. Never put credentials in the handover document.

Give each person their own authorized account where the system supports it. Shared identity makes it harder to understand who acted and to remove one person’s access later. A staff member should not need the founder’s password, email login, seed words, or hardware wallet merely to answer whether a customer has paid.

For any remaining shared dependency, state the limit honestly. If only one trained person can perform a particular task, the plan should include a pause or a properly authorized alternative. Calling a process covered does not create a second person with the necessary competence. The objective is reliable capacity, not an attractive organizational chart.

Give exceptions an owner and a stopping point.

The ordinary sale is rarely the hard part. Test a payment that arrives late, a customer who sends too little, a duplicate support request, and a refund destination that changes unexpectedly. The staff member should know what evidence to collect, what they may say to the customer, and which decision belongs elsewhere.

BTCPay Server’s current invoice guidance distinguishes base states from exceptions and explains the stages of its refund process. Creating a refund claim is not the same as completing a payout. A manually marked invoice is not independent proof that a payment confirmed. Use the actual system documentation to write the company’s procedure, then verify it against the installed configuration.

Do not let a support script promise an automatic remedy the business cannot deliver. A colleague can acknowledge a complaint, explain the review process, and request an invoice reference without deciding a disputed contract. Where legal rights or a significant dispute are involved, the escalation should reach the appropriate professional. The founder’s holiday does not suspend the company’s obligations to customers.

The matrix below uses fictional roles for a small business. Replace them with the company’s real people and approved authority. Add any monetary limits only after they have been agreed. A table is not a delegation document, and a technical permission is not a substitute for one.

Include a stop instruction for suspicious requests. The colleague should be able to pause a payout when the destination changes through an unverified channel, when the invoice cannot be matched, or when the request exceeds authority. That pause should trigger an identified response, not leave the customer indefinitely unanswered. A defined escalation protects both the customer experience and the company’s funds.

Fortnight operating-role worksheet
TaskMay view or prepareWho decides or signsWhen to pause
Customer payment querySupport checks invoice and orderNo spending decision needed for a status replyPayment evidence conflicts with order record
Routine invoiceOperations prepares from approved saleExisting commercial authority appliesCustomer or entity details differ from contract
Refund requestSupport records complaint and evidenceAuthorized manager decides; treasury executesDispute, changed destination, or limit exceeded
Supplier paymentFinance prepares matched invoiceApproved reviewer and authorized signersMissing approval or unverifiable bank or wallet change
System incidentTechnical operator investigatesNamed incident lead approves material actionRecovery would expose secrets or alter custody
Official correspondenceDesignated recipient logs and forwardsResponsible officer or professional respondsDeadline or subject lies outside delegated scope

Rehearse the fortnight without putting the treasury at risk.

Run a short exercise before the absence. Use fictional customers and amounts, a training environment where appropriate, and read-only records that have been stripped of unnecessary personal information. Nobody needs to move production funds to demonstrate that they can identify the right invoice, approval, and escalation route.

On the first exercise day, have support locate a fictional paid order and draft a response. On the second, introduce a late payment. On the third, ask finance to prepare a supplier request while one reviewer is unavailable. Later, introduce an official letter with a deadline, and a technical alert. These events should test the handoffs that currently depend on the founder.

Make the founder observe rather than rescue. If someone asks a question only the founder can answer, record it before providing help. Is the missing item a document, a policy decision, training, or authority? Each requires a different correction. Simply writing down the founder’s answer may not be enough if the person still lacks access to the evidence behind it.

Test communication failure as well. What if the nominated alternate does not respond during the expected working window? Who tells the customer there is a delay? Which supplier obligations require advance arrangements? The business should not rely on staff guessing whether silence means approval. A missed response should lead to a stated next step.

Check the accounting handoff at the end. A reviewer should be able to link the fictional customer order, invoice, payment, fee, and any refund decision. The company’s accounting professional should identify any required information that the operational process fails to preserve. Fixing the reference at the point of sale is usually easier than reconstructing it weeks later.

Record the exercise results in plain language. Name the task, the observed failure, the correction, and the person responsible. Keep a clear boundary between a demonstrated process and an unresolved assumption. A plan can still be used with a known limitation if the affected activity is paused or otherwise covered through an approved arrangement.

Make the return as orderly as the departure.

Before leaving, give the team one current handover with dates, contacts, scope, and escalation criteria. Link to the relevant policies instead of creating several competing copies. Make sure outside providers know the authorized contact for the fortnight where that change is appropriate. Do not tell a provider that a colleague has powers the company has not actually granted.

Keep an absence log that records decisions and exceptions rather than every routine message. Each entry should state what happened, who acted, what authority applied, and what remains open. This gives the founder a useful return briefing and gives the company a record independent of the founder’s memory.

If the founder does intervene, record that too. A holiday that appears successful because the founder quietly approved everything at night has not demonstrated independence. There is no need to turn that into a failure of the staff. It identifies where the planned roles, access, or confidence were insufficient and where the next improvement should focus.

On return, review temporary permissions and any delegated arrangements. Remove access that was granted only for the period through the normal authorized process, while preserving records that the company still needs. Confirm that unresolved customer or supplier matters have an owner. The end of the holiday should not strand an exception in someone else’s inbox.

Decide which improvements should become ordinary practice. A clear supplier-change verification procedure or a better invoice reference may help all year. A special temporary approval arrangement may need to end. Keep the distinction explicit so that a convenient two-week workaround does not become an unreviewed permanent transfer of responsibility.

The test is modest but meaningful: can the business fulfill its ordinary promises for a fortnight without relying on the founder’s identity, secrets, or constant availability? A complete answer may include a few activities that wait. Reliability comes from knowing those boundaries and honoring them, not from claiming that every conceivable event has been automated.

The whole picture

The Bitcoin Lawyer take

Use the rehearsal to find the first decision that depends on the founder. Delegate that decision through the company’s ordinary controls and leave signing access with the people who need it.

Bitcoin Lawyer can help connect operating responsibilities with the wider company and payment arrangements. Technical permissions need technical verification, and changes in corporate authority need the relevant professional review. The aim is a team that can do its agreed work with confidence, while exceptional decisions remain with the people qualified and authorized to make them.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “Can your Bitcoin business run for two weeks without you?” https://www.bitcoinlawyer.com/journal/bitcoin-business-founder-absence