Dweise Seller Records
A privacy-first desktop application for UK marketplace sellers. It would turn messy eBay, Vinted and other marketplace files into clear, reviewable records that the seller can understand and share with an accountant, without sending their financial records to Dweise.
The opportunity has credible customer pain, a timely UK regulatory backdrop and a strong fit with Dweise's existing records-processing direction. The proposed execution model is a local-first, self-service desktop application with optional encrypted backup later. Two decision gates protect the investment.
How evidence is labelled in this briefing
Confirmed findings are supported by the completed reports and their cited sources. Agreed directions reflect decisions taken during project discussions. Assumptions and open decisions must be tested. Points marked for advice must be confirmed by qualified professionals before launch. Every diagram in this briefing is accompanied by a written equivalent, so no information depends on the graphic rendering.
Executive summary
The opportunity in plain language, the recommended approach, the money involved and what has not yet been proved.
The records problem is real
Marketplace sellers receive net payouts after fees, postage, refunds, advertising and adjustments. These figures are difficult to reconstruct into understandable business records.
Build a private desktop tool
The initial product would process files locally using a Go-based desktop application. User records would not be uploaded to Dweise by default.
Serious sellers will pay
The strongest likely customers are genuine traders with many transactions, multiple platforms or an upcoming accountant, tax or HMRC deadline. Payment still needs to be proved.
The problem being solved
Selling online is easy. Producing accurate, understandable records from marketplace files is not.
What sellers see
- A bank payout that is lower than the value of their sales.
- Separate files for orders, payouts, fees, refunds and labels.
- Personal-item sales mixed with genuine trading activity.
- Missing or unclear stock-cost and postage evidence.
- Different formats across eBay, Vinted, Etsy, Depop and other platforms.
What they need
- A clear total for gross sales, not merely net bank receipts.
- Fees, refunds, postage and other deductions separated properly.
- Unmatched or uncertain items highlighted for review.
- A record of where every figure came from.
- A clean summary that an accountant can understand.
Written equivalent
- Marketplace activity: orders, fees, refunds and postage labels are generated as the seller trades.
- Different exports and statements: each platform provides its own file formats, which do not match one another.
- Net bank deposits: money arrives as a single net figure that does not explain how it was calculated.
- Spreadsheets and guesswork: the seller reconstructs figures manually, and the accountant asks questions the seller cannot answer.
- Dweise Seller Records: normalises the files, reconciles them, asks the seller to review uncertain items, and exports a clear record.
Target users and current pain points
The opportunity is not aimed at everyone who sells an item online. It is aimed at people whose selling activity has become a genuine records problem.
Serious marketplace trader
A UK sole trader or side-business seller with repeated buy-to-resell, make-to-sell or commercial activity and enough transactions to make manual record keeping painful.
Accountant or bookkeeper
Receives a cleaner, traceable pack instead of several unexplained spreadsheets. In version 1 they are a referrer and a recipient of output, not a user of the software. See section 06.
Mobile companion user
Uses a phone to capture receipts, add stock evidence, review unresolved items and view summaries while the desktop remains the main records workspace.
The proposed product and how it would work
A downloadable desktop application would organise records locally. The server would initially handle licences and updates, not the seller's financial data.
Dweise Seller Records
A simple local workspace that imports marketplace files, converts them into a common records format, highlights questions and generates useful summaries.
Proposed technology direction
Final technical choices will be documented in the Architecture Decision Record after stakeholder agreement on the product direction. The target operating system for version 1 is an open decision (see section 15).
Written equivalent
- Import files: the seller selects marketplace exports and payout statements from eBay, Vinted and their bank.
- Normalise: platform-specific columns are converted into one common transaction model.
- Reconcile: gross sales, fees, refunds and postage are joined to the actual bank payouts.
- Review: the seller confirms uncertain classifications, including personal versus trading items.
- Export: summaries, an exception list, an evidence log and an accountant-ready pack are generated.
All five steps run on the user's own computer. Dweise does not receive the records.
Core features and intended user journey
The MVP should complete one bounded job well: transform marketplace exports into an understandable, reviewable records pack.
Workspace setup
Create a local workspace for a business and tax year. Choose the marketplaces used.
Guided import
Select marketplace exports and payout files. The app identifies the source and validates the format.
Automatic normalisation
Convert platform-specific columns into a consistent record of orders, fees, refunds and payouts.
Reconciliation
Explain how gross sales become net payouts and show anything that does not match.
User review
Ask simple questions about personal sales, business sales, stock costs and missing evidence.
Reports and handover
Generate sales, fees, refunds, postage, exceptions, evidence logs and accountant-ready exports.
Written equivalent
- The seller installs Dweise Seller Records.
- They create a business workspace for the relevant tax year.
- They import their eBay and Vinted files.
- The application asks whether any records are uncertain.
- If no: the seller goes straight to the review summary.
- If yes: the seller answers guided questions and attaches evidence, then reaches the review summary.
- They export the accountant-ready pack.
- They continue using the same local workspace for the next period.
Delivery options
Three operating models were considered. They differ significantly in regulatory exposure, customer experience and scalability.
The seller imports records, confirms classifications and owns the output. Dweise supplies software rather than completed books or tax decisions.
Dweise staff would receive files, decide classifications and return finished records. This is likely to be accountancy-service activity requiring anti-money-laundering supervision. See section 08.
Accountants can refer sellers and receive exports. They cannot use the desktop product across multiple clients in version 1. See the architecture tension in section 07.
| Option | Who makes the decisions? | Main advantage | Main concern | Current position |
|---|---|---|---|---|
| Self-service | The seller | Private, scalable and consistent with a software product. | Must be genuinely usable without staff doing the bookkeeping. | Selected |
| Managed service | Dweise staff | Can solve difficult cases and create early cash. | AML supervision, staffing and margin exposure. | Deferred |
| Accountant partner | Seller, with the practice reviewing | Distribution, trust and professional review. | No multi-client product exists until a professional edition is built. | Referral channel only in v1 |
The architecture tension, stated plainly
This section exists because the earlier research and the chosen architecture point in different directions. Stakeholders should see the conflict and the resolution rather than discover it later.
The resolution proposed
Accountants are a referral and recipient channel in version 1, not users of the software. They send clients to the product, and they receive a clean export. They do not log in, and there is no multi-client workspace until a professional edition is justified by evidence.
This is honest and defensible. What would not be defensible is describing accountants as a primary customer while shipping nothing they can operate.
What this costs, and the trigger to revisit
- The strongest distribution channel is only partly monetised in year one.
- A professional edition would likely need a hybrid or cloud architecture, which is a second build.
- If the pilot shows practices, not sellers, are the ones willing to pay, the local-first decision must be reopened at the week 12 gate rather than defended.
This is the single most likely reason the current plan would need to change.
Privacy-first and local-first direction
The recommended architecture is local-first rather than pure cloud software. Sensitive records remain on the user's computer unless the user explicitly enables an encrypted service later.
Local-first desktop application
- Financial records and evidence stored locally.
- Imports and reconciliation processed on the user's device.
- Works without continuous internet access.
- Lower central data-storage and breach exposure for Dweise.
- Strong privacy message for financially sensitive information.
Optional encrypted backup and sync
- The app encrypts a backup before upload.
- Dweise stores opaque data it cannot read.
- The user can restore records after loss or device failure.
- A later mobile companion could exchange encrypted changes.
- Full multi-device synchronisation comes after backup is proven.
Written equivalent
| Zone | Contains | Sees seller records? |
|---|---|---|
| The user's computer | Desktop application, Go records engine, encrypted local database, encrypted evidence files, and a manual encrypted backup or export included in the MVP. | Yes, this is the only place records live. |
| Minimal Dweise cloud | Licence status, signed application updates, and non-sensitive parser definitions. | No. Licence, version and configuration data only. |
| Optional future services | Client-side encrypted backup, and later an encrypted device-sync relay. | No. Data is encrypted before it leaves the device, so Dweise cannot read it. |
Cloud software compared with local-first
| Consideration | Pure cloud software | Local-first with thin cloud |
|---|---|---|
| User trust and privacy | Records uploaded to Dweise. | Records remain on the user's device by default. |
| Installation | Open a browser and start. | Requires download, code signing and updates. |
| Cloud cost and data liability | Higher as storage and processing grow. | Low central storage and strong data minimisation. |
| Offline use | Limited or complex. | Natural. |
| Accountancy practice workflows | Easier for teams and multi-client access. | Not served in v1. Requires a later professional edition. |
| Strategic differentiation | Similar to many accounting tools. | Clear privacy-first position. |
UK tax, MTD, AML and regulatory considerations
Regulation creates urgency, but it also defines what the product may claim and what Dweise must not do without appropriate professional arrangements.
The anti-money-laundering boundary, and why self-service sits outside it
Under regulation 11 of the Money Laundering Regulations 2017, an external accountant is a firm or sole practitioner who by way of business provides accountancy services to other persons. HMRC treats accountancy services as recording, reviewing, analysing, calculating and reporting on financial information for other people, and states this includes bookkeeping.
HMRC's registration guidance also lists an exclusion for businesses providing software or support services, provided they do not analyse or prepare the financial information themselves. That exclusion is the basis for the recommended model.
| Model | AML supervision likely? | Customer due diligence? | Position |
|---|---|---|---|
| Self-service software, seller confirms and owns output | No | Not required | Recommended |
| Dweise decides classifications and returns books | Yes | Required on every client | Deferred |
| Sold to, or operated under, a supervised practice | No, the practice is the regulated party | The practice performs it | Later option |
| Area | What the research supports | Product implication | Status |
|---|---|---|---|
| Platform reporting | Digital platforms report qualifying seller information to HMRC. Reporting does not automatically mean the seller owes tax. | Do not treat a platform threshold as a tax-liability rule. | Confirmed |
| Making Tax Digital | MTD for Income Tax began for qualifying income above £50,000 from April 2026, reducing to £30,000 in 2027 and £20,000 in 2028. | Digital records become increasingly relevant, but the MVP organises records rather than filing updates. | Confirmed |
| HMRC does not supply MTD software | HMRC publishes a list of recognised third-party software but does not provide its own MTD for Income Tax product. | There is no free official filing tool competing directly at the filing layer, though free third-party tools exist. | Confirmed |
| Personal sales versus trading | Marketplace receipts alone do not determine whether activity is taxable trading. | The app must ask the user to confirm the nature of activity and must not decide tax liability. | Confirmed |
| Tax adviser registration | Mandatory Tax Adviser Registration begins on 18 May 2026. It applies where a business interacts with HMRC on another person's tax affairs and is paid for doing so. | Because the MVP never contacts HMRC on a seller's behalf, registration is not expected to apply. This must be confirmed if the product later adds filing. | Advice required |
| UK GDPR and ICO | Dweise still processes licence and account data, and may later hold encrypted backups. The ICO data protection fee for a small organisation is £52 (tier 1). | Privacy notice, security controls, data mapping, contracts and ICO registration remain necessary even with local-first storage. | Advice required |
| Consumer software and subscriptions | Digital-product quality, cancellation, renewal and clear-pricing requirements apply. | Design annual licensing and any future backup subscription with simple renewal and exit. | Advice required |
Market evidence, competitors and demand signals
The market is not empty. The opportunity exists in a narrower position between spreadsheets and full ecommerce accounting integrations.
Written equivalent
- About 4 million seller reports were received by HMRC for 2025, according to a Freedom of Information request reported by BDO. This includes casual sellers, non-taxable disposals and duplication across platforms.
- Sellers with repeated or material trading activity are a smaller subset.
- Genuine traders needing defensible business records are smaller again.
- Those poorly served by current tools excludes people already using an accountant or a full ledger.
- Those who will actually pay is the real target market and remains unproven.
Evidence supporting demand
- HMRC reportedly received close to four million marketplace seller reports for 2025, up sharply on the prior year, showing the scale of platform reporting.
- MTD progressively brings more sole traders into digital record keeping.
- HMRC has been contacting people about possible undeclared online income.
- Seller discussions describe manual spreadsheet work, unexplained payouts and high volumes of adjustments.
- Existing paid integrations and low-cost templates show people already spend money on related problems.
What remains unproved
- How many serious sellers will pay for a standalone local application.
- Whether an annual price near £149 is acceptable against a competitor charging £49 once.
- Whether the app can normalise at least 80% of real records automatically.
- Whether accountant referrals can produce customers economically.
- Which marketplace combination creates the strongest initial demand.
| Competitor category | Examples | Price | Strength | Opening for Dweise |
|---|---|---|---|---|
| Settlement-to-ledger tools | A2X, Link My Books | From about £16 to £23 per month, plus a ledger subscription | Strong automation into Xero and QuickBooks. | Serve sellers who do not want a full ledger, and cover Vinted and Depop, which neither supports. |
| Single-platform seller tools | Vinta | £20 per month, or £49 once for lifetime access | Focused Vinted record tracking with UK-oriented content. | Multi-platform reconciliation, a private desktop workspace and an evidence trail. |
| General accounting software | Xero, QuickBooks, FreeAgent, ANNA | About £10 to £33 per month | Broad ledgers, bank feeds and tax workflows. | Explain marketplace payouts without a full accounting implementation. |
| DIY templates | Reseller spreadsheets on Etsy | £5 to £15 once | Cheap, familiar and flexible. | Automate imports, reconciliation, exceptions and evidence tracking. |
| Specialist accountants | Ecommerce and online-seller practices | Bespoke fees | Professional judgement and filing support. | Become a referral channel and reduce their client clean-up work. |
Why this opportunity was selected
Marketplace-seller records emerged from a wider vertical scan and remained the strongest fit after more critical checks.
Strategic fit
Reuses the import, categorisation, exception and reporting concepts already relevant to Dweise Landlord.
Timely UK pressure
Platform reporting, HMRC correspondence and MTD increase attention on record quality.
Clear initial job
The MVP can solve a bounded records problem without replacing accounting software.
Expansion path
The same records engine could later support landlord, seller and sole-trader products.
Written equivalent
One shared Dweise records engine (import, normalise, classify, resolve, evidence, export) supports three products:
- Dweise Landlord: property income and expenses. Shipping today.
- Dweise Seller Records: marketplace sales and payouts. Proposed in this briefing.
- Dweise Sole Trader: general trading records. A future concept only.
The opportunity is more valuable because it contributes to a reusable platform rather than an isolated application.
Key decisions already made
These are the current project directions. Some remain subject to validation or professional confirmation.
Build versus buy
The general Dweise strategy favours buying neglected products where possible. This opportunity does not currently offer a clean acquisition shortcut.
Why building is currently preferred
- The core differentiator is multi-platform, ledger-free reconciliation.
- The local-first privacy architecture is not available off the shelf.
- Dweise can reuse concepts and components from the landlord product.
- A small upload-based MVP can be tested without building the whole platform.
What an acquisition could provide
- Existing users and seller-specific knowledge.
- A parser or workflow for one marketplace.
- Search traffic, content and an established brand.
- Faster entry into a particular seller community.
| Potential target | Useful asset | Limitation | Current conclusion |
|---|---|---|---|
| Vinta | Vinted-specific product, users and content. | Single-platform, actively maintained rather than neglected, and not confirmed for sale. | Exploratory conversation only |
| Taxomate | Marketplace settlement and VAT logic. | Ledger-oriented and does not solve the local-first Vinted and Depop opening. | Partial strategic fit |
| Small spreadsheet products | Audience, content and seller terminology. | Little defensible technology and low-price customers. | Not a substitute for validation |
Commercial model, pricing and revenue potential
The business should earn recurring revenue even though customer records remain local. Pricing is a working assumption that the pilot must test.
Founding licence
Covers the first tax year plus twelve months of parser and application updates. Sold during the pilot to prove willingness to pay at a realistic price.
Annual licence
Renewal covering supported marketplace parsers, updates, the current tax year's reports and offline use with a reasonable grace period.
Private backup
Optional client-side encrypted backup, retention history and device-loss restore. Dweise would be unable to read the stored records.
The pricing risk, stated honestly
The nearest comparable product, Vinta, charges £20 per month or £49 once for lifetime access. This cuts two ways and both must be tested.
If pilot sellers consistently refuse £149, the fallback is not a discount but a narrower, cheaper product, or a shift to the accountancy-practice buyer, which would reopen the architecture decision in section 07.
Revenue scenarios
Illustrative only. These are scenario ranges at an average of about £149 per customer per year, not forecasts.
The realistic planning case is the established scenario: a focused, owner-operated business of £100k to £300k a year. The upper case requires an accountant channel or a marketing engine that does not exist today.
Proposed validation budget and timeline
This is the specific investment being requested. The figures are proposed by the project team and should be confirmed or amended by stakeholders.
Cash budget to a go or no-go decision
| Item | Purpose | Cost |
|---|---|---|
| Written AML and regulatory opinion | Confirm the self-service boundary and marketing language | £1,200 |
| ICO data protection fee (tier 1) | Statutory registration | £52 |
| Windows code-signing certificate | Installable software without security warnings | £350 |
| Apple Developer Program | Only if a macOS build is in scope | £79 |
| Seller discovery incentives | 10 interviews with real file sharing at £30 | £300 |
| Accountant pilot time | 2 practices at £200 for structured feedback | £400 |
| Landing page, domain and email | Recruitment and credibility | £100 |
| Small paid recruitment test | Test whether pilot users can be reached at sane cost | £400 |
| Contingency (about 20%) | Scope and price movement | £619 |
| Proposed total | £3,500 | |
Sensible range: £3,000 to £4,500. The largest single item is the legal opinion, and it is the one item that should not be cut, because it de-risks the entire operating model.
Time and gates
Twelve weeks to a decision, consistent with the 90-day plan in the AML and acquisition report. Founder time is the larger real cost and is shown separately below.
| Period | Activity | Gate |
|---|---|---|
| Weeks 1 to 2 | Recruit sellers and practices, collect sample exports, commission the legal opinion, test price reaction. | Gate 1 at week 3 |
| Weeks 3 to 10 | Build the local MVP: import, normalise, reconcile, review, export, encrypted local backup and signed updates. | Build only if gate 1 passes |
| Weeks 10 to 12 | Run the paid pilot with real files and real payments. Measure the gates in section 16. | Gate 2 at week 12 |
| Week 12 | Go or no-go. Re-score the opportunity using evidence. Approve the ADR and implementation plan, or stop. | Decision |
Key risks, assumptions and pass or fail gates
The opportunity should proceed only if the paid pilot resolves the commercial and technical questions below.
| Issue | Current position | How it will be tested or resolved | Type |
|---|---|---|---|
| Seller willingness to pay | Likely among serious sellers, but not proved, and anchored against a £49 lifetime competitor. | Charge £149 during the pilot. Do not rely on survey interest. | Assumption |
| Import reliability | Exports are feasible, but formats and completeness vary. | Test real files and require at least 80% automatic normalisation. | Assumption |
| An incumbent adds Vinted or Depop | Link My Books and A2X cover neither today. That is the basis of the opening. | Monitor their channel lists monthly. Treat coverage parity as a material strategic event. | New in v2 |
| Vinta expands beyond Vinted | Vinta is actively maintained and already owns the Vinted niche. | Watch its roadmap. If it goes multi-platform first, the differentiator narrows sharply. | New in v2 |
| Operating system scope | Undecided. Sellers likely skew Windows, but macOS adds notarisation cost and time. | Decide at gate 1 from pilot recruitment data. Ship one platform first. | New in v2 |
| Build estimate | Eight weeks for engine, shell, two parsers, reconciliation, review interface, reports, backup and signed updates is achievable but tight. | Protect scope ruthlessly. Cut the second marketplace before cutting reconciliation quality. | New in v2 |
| Vinted and Depop access | Official general financial API access is constrained. | Use user exports first and avoid unsupported scraping. | Confirmed |
| Bookkeeping and AML boundary | Self-service appears to sit outside supervision, but guided onboarding could compromise it. | Obtain written advice on the exact workflow, marketing language and pilot onboarding script. | Advice |
| Local data loss | Local-first creates a device-failure risk. | Provide manual encrypted backup in the MVP and optional cloud backup next. | Direction |
| Support burden | Missing evidence and unclear activity could create high support costs. | Measure handling time, unresolved rate and common questions. | Assumption |
| Accountant channel | Promising but not proved, and not served by the v1 product. | Pilot with at least two specialist practices using exports only. | Assumption |
Pass or fail gates for the pilot
| Gate | Pass condition | Why it matters |
|---|---|---|
| Payment | At least 5 sellers pay £149, or 2 practices commit real client files. | Separates anxiety from genuine demand. |
| Automation | At least 80% of transactions normalised or matched automatically. | Manual work destroys the margin. |
| Time | Median handling under 90 minutes per customer. | Tests whether it scales beyond consulting. |
| Evidence burden | Fewer than 10% of records need extended chasing. | Missing purchase evidence destroys unit economics. |
| Access | The workflow succeeds using exports or supported APIs only. | Avoids fragile scraping and enforcement risk. |
| Regulation | Written AML and data-protection position obtained and satisfied. | Stops a good pilot becoming a liability. |
Recommended MVP scope
The MVP should prove demand and data handling without prematurely building cloud sync, tax filing or a complete accounting product.
- Local business and tax-year workspace.
- Encrypted local database and evidence store.
- eBay and Vinted file imports.
- Sales, fees, refunds, postage and payout normalisation.
- Payout reconciliation and unmatched-record queue.
- User-confirmed personal versus trading review.
- Missing-evidence and exception list.
- Accountant-ready summaries and source-file register.
- Manual encrypted local backup and export.
- Signed application updates and basic licence activation.
- Direct HMRC or MTD submission.
- Tax advice or automatic tax-liability decisions.
- Dweise-managed bookkeeping.
- Bank-feed integrations.
- Full cloud records storage.
- Multi-device concurrent synchronisation.
- A full mobile version.
- Every marketplace and direct API integration.
- Multi-user accountancy-practice administration.
Phased roadmap
Each phase should be approved only when evidence from the previous stage supports it.
Validate the proposition
Recruit sellers and accountants, collect sample exports, confirm legal boundaries, test pricing and define gates.
Build the local MVP
Deliver import, normalisation, guided review, local storage, reports, encrypted backup and signed updates.
Private backup and beta
Add client-side encrypted cloud backup, improve parsers, refine onboarding and begin accountant referrals.
Companion and professional
Add receipt capture, mobile review, optional encrypted sync and a professional edition if evidence supports them.
Written equivalent
- Paid validation (payment and real files) leads to the Local MVP covering eBay and Vinted.
- From the MVP the path branches in two directions:
- Professional edition for accountancy practices, only if practices prove they will pay.
- Encrypted backup for restoring records after device loss.
- Encrypted backup leads to a mobile companion for capture and review.
- The mobile companion may lead to full synchronisation, but only if justified.
Benefits to customers and stakeholders
The opportunity creates different forms of value for sellers, accountants and Dweise.
For sellers
- Understand where the money went.
- Keep sensitive records private.
- Reduce spreadsheet work and repeated calculations.
- Identify missing records before deadlines.
- Give an accountant a clearer handover.
For accountants
- Receive consistent, traceable client records.
- Spend less time reconstructing marketplace payouts.
- See unresolved items before beginning professional work.
- Refer clients to a self-service preparation tool.
- Potentially use a future practice edition.
For Dweise stakeholders
- Creates a second vertical on shared records technology.
- Builds recurring revenue without storing raw records centrally.
- Strengthens the privacy-first position.
- Opens future seller, sole-trader and accountant products.
- Provides a measurable, staged investment path.
Immediate next steps and decisions required
The next stage should answer the remaining commercial, regulatory and product questions before the ADR locks in technical choices.
Immediate actions (weeks 1 to 2)
- Recruit five serious sellers and two marketplace-specialist accountants.
- Obtain consented sample exports from eBay and Vinted.
- Commission the written AML and data-protection opinion, including the onboarding script.
- Test the proposition and the £149 price with real sellers.
- Create a low-fidelity prototype of the import, review and export journey.
- Prototype the canonical marketplace transaction model in Go.
- Decide the target operating system for version 1.
- Continue a light, logged-in acquisition scan without delaying the pilot.
Stakeholder decisions required
- Approve or reject the local-first product direction.
- Approve the £3,500 validation budget and the twelve-week timeline.
- Confirm the accountant position: referral channel in v1, not a software user.
- Confirm the first-user focus: serious multi-platform sellers.
- Confirm the initial platforms: eBay and Vinted, subject to sample files.
- Agree the regulatory boundary: self-service records organisation only.
- Agree the gate 1 and gate 2 criteria and who signs them off.
Approve a twelve-week paid validation phase with a cash budget of £3,500 and the local-first, self-service product direction. Defer full engineering commitment until sellers pay, real exports process reliably, accountants value the output and the regulatory model has been professionally confirmed. Stop at week 3 if the first gate fails.
Source base
This briefing consolidates the project's completed reports and discussion decisions. The underlying reports contain the detailed research, citations and caveats.
Compared marketplace-seller records, funeral software and embroidery shop management. Established marketplace records as the strongest strategic fit.
Revised the opportunity score, narrowed the market gap, reviewed competitors, data access, pricing and validation gates.
Compared self-service, managed and accountant-partner models, assessed build versus buy, and set the 90-day plan this timeline follows.
Project decision record, not yet written up as a separate document. Selected a Go and Wails local desktop application, a minimal cloud control plane, optional encrypted backup, and sync only after backup. Action: write this up so the decision has a citable record.
Selected external sources
Official source for the £50,000, £30,000 and £20,000 qualifying-income thresholds.
Platform reporting, and the distinction between being reported and owing tax.
The statutory definition of an external accountant used in the boundary assessment.
Scope of accountancy services and the software provision exclusion. Professional confirmation still required.
Applies from 18 May 2026 where a paid business interacts with HMRC on another person's tax affairs.
Tier 1 fee of £52 for small organisations, plus UK GDPR duties.
Evidence that official financial and payout integration may be possible later.
Evidence supporting the opening around Vinted and Depop.
Vinted-only coverage at £20 per month or £49 once. The key pricing benchmark.
Freedom of Information figures behind the demand funnel in section 10.