A £1 SaaS Deal Can Still Be Expensive: Price the Transfer Before You Bid

A low starting price can make a software acquisition feel almost risk-free. It is not. A £1 opening bid, nominal transfer price or “distressed asset” label tells you what it may cost to enter the deal—not what it will cost to take control, make the product safe, keep it online and become accountable to customers.

For a small operator, the handover can be more expensive than the asset. Code may need moving, accounts may need rebuilding, licences may not follow the product, customer data may require a lawful transfer process, and undocumented systems may need urgent repair. The right question is therefore not “Can I afford the bid?” but “Can I afford ownership after the bid?”

The price is only one line in the acquisition budget

A useful acquisition budget separates four numbers:

• Purchase price: the amount paid to acquire the stated assets or entity.
• Transfer cost: the professional and technical work required to move control.
• Stabilisation cost: what it takes to keep the product secure and functional during the first 90 days.
• Risk reserve: money held back for defects, missing documentation, customer obligations and supplier changes.

The first number is visible in an auction or listing. The other three often become clear only after document review and technical inspection. That is why an unusually cheap deal can still be unaffordable.

First establish what is actually being sold

“SaaS business” is not a precise transfer description. A seller might be offering a company, selected assets, a source-code licence, a domain and brand, or merely access to a hosted application. Those are materially different deals.

Before setting a bid ceiling, ask for a written asset schedule. It should identify the source-code repositories, domains, trademarks, databases, documentation, design files, analytics properties, customer contracts, supplier accounts and any physical or financial liabilities included. It should also identify what is explicitly excluded.

The UK Government’s data-room checklist describes a data room as a central repository for the legal, financial, operational and commercial information investors need for due diligence. That principle scales down well: even a tiny transaction needs enough evidence to distinguish a transferable business from a folder of files.

If your main concern is whether a licence permits resale, modification and client transfer, use the more detailed MaryChuks guide to white-label SaaS licence and transfer due diligence. The focus here is the separate financial question: how much cash and work will be needed after those rights are understood?

Build a transfer-cost ledger before you bid

Do not use a single “migration” estimate. Price each control point independently, because some assets transfer while others must be recreated.

Control point	Evidence to request	Possible transfer work
Code and deployment	Repository ownership, branches, dependencies, build instructions and deployment history	Repository transfer, secret rotation, build repair, new pipelines and access review
Domain and brand	Registrar record, renewal date, trademark status and brand-asset inventory	Registrant change, DNS migration, email authentication and redirect testing
Cloud and suppliers	Invoices, service list, regions, quotas, contracts and cancellation terms	New accounts, data migration, reserved-capacity changes and duplicated running costs
Payments	Account owner, settlement history, disputes, refunds and processor restrictions	Ownership change or new onboarding, identity checks, webhook changes and reconciliation
Customer data	Privacy notices, lawful basis, consent records, retention rules and processor contracts	Due diligence, notices, processor updates, migration controls and deletion work
Security	Access list, vulnerability history, backups, incident log and key inventory	Credential rotation, dependency updates, penetration testing and backup validation
Customer obligations	Terms, service levels, prepaid commitments, open tickets and promised features	Support cover, refunds, remediation, communication and delivery work

Platform transfer mechanisms also have conditions. GitHub’s repository-transfer documentation, for example, explains what moves with a repository and warns that some features can change when a private repository moves to a different account or plan. Stripe’s official support material likewise says the current owner can transfer Stripe account ownership, but that possibility should not be mistaken for evidence that a particular account is eligible, compliant or free of reserves and disputes.

Treat customer data as a transfer project, not a free asset

A customer database may be commercially valuable, but it is also a responsibility. The UK Information Commissioner’s Office says data sharing may occur as part of an acquisition, merger or other organisational change, and that data-protection considerations should form part of due diligence. Its data-sharing advice also stresses the need to consider what people were told and whether the proposed use remains fair and lawful.

Budget for legal review, privacy-notice updates, processor-contract checks, data mapping, secure migration and deletion of material you have no reason to retain. If the seller cannot explain how the data was collected, where it is stored or who can access it, do not assign the database a positive value until the problem is resolved.

Illustrative calculation: the £1 deal that needs £2,700

This is an illustrative calculation, not a quote or a record of an actual transaction. Suppose a buyer can acquire a small software asset for £1. The product has no employees, but the buyer needs limited legal review, technical handover and a 90-day safety buffer.

Item	Illustrative amount
Purchase price	£1
Legal and IP review	£600
Developer handover: 12 hours × £45	£540
Security and access review	£350
Migration and relaunch work	£400
Hosting and tools for 90 days	£270
Risk reserve: 25% of £2,160 non-purchase costs	£540
Total cash requirement	£2,701

The important insight is not the exact total. It is the ratio: the transfer and stabilisation budget is 2,700 times the nominal purchase price. A buyer who evaluates only the £1 headline will be undercapitalised before the first customer problem arrives.

Owner time belongs in the model too. If you expect to spend 60 hours on documentation, support and migration, give those hours a realistic opportunity cost—even if no cash leaves the bank. Otherwise, a “cheap” acquisition can quietly consume the time needed to operate your existing business.

Set a bid ceiling from contribution value, not excitement

A simple discipline is:

Maximum bid = conservative 12-month contribution value − transfer cost − stabilisation cost − risk reserve

“Contribution value” means the cash the product could generate after direct delivery costs, refunds, payment charges, support and other variable costs—not gross revenue and not a seller’s asking price. If you need a refresher, MaryChuks has a separate guide to calculating contribution margin per order.

Use a conservative scenario. Reduce claimed revenue where it cannot be reconciled to processor statements, bank receipts or subscription records. Exclude customers who have cancelled, are overdue or depend on a founder relationship that may not survive the sale. Then test what happens if revenue falls while migration costs rise.

A low-price acquisition may suit you when…

• You can verify ownership and transferability before money changes hands.
• You or a trusted specialist can inspect the code, infrastructure and security posture.
• You have enough cash to fund handover and 90 days of stabilisation without relying on immediate sales.
• The product complements capabilities, customers or distribution you already possess.
• You are comfortable treating the deal as a controlled learning investment rather than guaranteed income.

You should probably avoid it when…

• You need the acquired product to pay your bills immediately.
• The seller cannot provide a precise asset schedule or proof of control.
• Critical services sit in personal accounts that cannot be transferred cleanly.
• Customer contracts, privacy records or refund obligations are unclear.
• The code runs only because the seller knows undocumented fixes.
• Your budget covers the bid but not independent review, migration and contingency.

Real alternatives to buying the whole asset

Walking away is a valid decision. So is buying less. You might negotiate for the domain and brand without the customer data, license selected code rather than acquire the company, pay for a documented handover milestone, or build a narrow replacement using tools you already operate.

A staged transaction can also reduce uncertainty where the marketplace and agreement support it: verification first, then repository and domain control, then final payment after specified handover evidence. Do not assume that escrow, warranties or post-sale support exist merely because a platform describes them; read the actual transaction terms and confirm who is responsible for each milestone.

Use a go/no-go gate before placing any bid

• Go: the asset schedule is specific, evidence is accessible, transfer steps are documented, liabilities are bounded and the total budget still fits.
• Pause: value may exist, but a repository, payment account, data set, key contract or security assumption still needs verification.
• No-go: ownership is unclear, critical access is non-transferable, customer obligations cannot be quantified, or the deal only works if every optimistic claim is true.

The most useful number in a low-price SaaS acquisition is rarely the opening bid. It is the all-in amount you are willing and able to lose while still completing a responsible transfer. Price that figure first, and the bargain headline becomes easier to judge.

Optional next step: MOC Marketplace is part of the MaryChuks.com business ecosystem. If you want to see the current marketplace gateway, browse MOC Marketplace. This is a general discovery link, not a recommendation of a particular listing; verify the listing, evidence, terms and transfer path yourself before making an offer.

---