Business Regulation

A product team's list of work is a list of features. Invite screen, payment integration, notification settings. The conditions attached to selling never show up on that list, because nobody requests them and nothing breaks without them. The filing you need on the day payments go live, the evidence a marketing claim requires, the sentence that belongs on the refund screen — all of it is written down somewhere outside the company, and nobody owns the job of copying it in.

So the conversation always starts late. During the week payments are supposed to ship, the payment processor comes back saying one document is missing, and only then does somebody ask whether the company ever filed it. The filing takes three or four business days, which everyone learns in that meeting, after the launch date has already gone out. Marketing runs the same way. A landing page goes live claiming the company is number one in its category, a regulator or a competitor asks what that claim is based on, and the answer turns out to be nothing. The line had been reviewed three times by then, but for tone rather than for evidence, because nobody in those reviews was looking for that.

Smaller companies get the worse end of this. A forty-person company has nobody whose job is reading law, so it often doesn't know that something exists to be known. Yet when a rule does catch it, more stops. One blocked payment method takes the whole month's revenue with it, while a large company loses a line item.

Pulling the scattered obligations under one name changes two things. The first is timing: instead of finding out after an incident, a team opens the list when it decides what to sell and how to charge for it. The second is ownership. A list with a name has somebody maintaining it, and checking it becomes a step before a feature ships rather than a reaction afterward.

It also settles what the word covers. How personal information gets collected and deleted belongs to the personal data protection branch next door, and how security runs as a process belongs to security operations. What sits here are the conditions that attach to being in this business at all: what you file, what you display, what you are allowed to claim, and what you owe someone who wants their money back. That also separates it from contracts. Contract terms are a promise between two parties and either side can negotiate them; regulation is a floor nobody can agree their way beneath, so a customer saying it's fine changes nothing.

The terms filed under business regulation split in two. On one side are the filings you do once to open the door. On the other are the laws that stay switched on for as long as you keep selling.

The filings announce to the outside world that the business exists. There are two, each a day of paperwork, and skipping either one blocks everything downstream.

1. Business registration — telling the tax authority you have started trading and receiving a number in return. The number is what lets you issue tax invoices, and corporate customers can't put a purchase through approval without one. It works the same way whether you trade as an individual or set up a company, and it is normally the first of these steps anyone takes, since the rest of them ask for the number it produces.
2. Online sales report — a separate filing that tells the local authority you sell goods or services over the internet. The number that comes back goes in the business details at the bottom of the site. Payment processors check for it during review, so a missing filing stops card payments dead on the day you try to add them.

The laws are the conditions that stay on. There are seven, and they sort by where they bite: on the transaction itself, on how you talk about the product, on the screens you build, and on people and money.

1. E-commerce act — sets out what a seller has to tell a buyer before taking money. Who is selling, what the price is and when it leaves the account, and how to cancel. Of everything here, this is the law that lands most directly on screen design.
2. Consumer protection — sets the window for changing your mind and the conditions for a refund. For anything sold by subscription it shows up as a requirement that cancelling be about as easy as signing up. A flow where joining is one button and leaving means emailing support fails here.
3. Advertising regulation — asks for evidence behind the sentences describing a product. Words like first, only, and number one need something you can point at, and free has to mean free without conditions attached. Reviews you paid for have to say so instead of sitting alongside unpaid ones.
4. Accessibility law — requires that people with disabilities can use the service. Whether a screen reader announces what a button does, whether someone can get from signup through checkout with a keyboard and no mouse. Sell to the public sector and the same requirements come back as contract terms.
5. Labor law — governs the conditions under which you employ people. When a written contract has to exist, what a probation period does and doesn't change, what procedure applies when someone leaves. It attaches to the team rather than the product, which is why builders miss it most often.
6. Working hour cap — a statutory ceiling on how many hours a week a person can work. The habit of absorbing a slipped date by working two heavy weeks before launch runs into it. Staying under the ceiling means adding people or cutting scope, so of the seven this is the one that reaches the schedule first, long before anyone files anything.
7. Electronic financial transactions act — governs the movement of money itself. Holding card details yourself carries enough conditions that most small companies route around them by using a payment processor. Build anything that takes money before delivery, such as prepaid credits, and the requirements step up again.

The two groups run in order. The filings open the door and the laws govern every day after that, which is also why they get checked on different rhythms. The filings are a one-time pass at the start. The laws come back every time a feature changes: touch the payment method and numbers 1 and 7 reopen, edit a pricing sentence and number 3 does, move the cancel flow and number 2 does.

You rarely deal with all seven at once, because what applies depends on how you sell. A company that only signs contracts with other businesses barely touches the first two filings, since contract terms do that work instead — but the day it starts charging individuals by card, both apply head-on. That is why adding payments to a product that used to be free is the day this whole list gets opened for the first time. The same thing happens at a smaller scale whenever the business changes shape — selling in a new country, opening a self-serve plan, or hiring the first employee instead of contracting the work out.

"We need the online sales filing before we can ship payments. The processor won't clear review without that number."

Development being finished doesn't launch anything if the paperwork is missing, so the order of work has to change.

"That line breaks advertising rules. If we're claiming number one, we have to name the survey it came from."

Not a request for softer wording — either the claim gets evidence next to it or it comes out.

"Auto-charging after the trial is fine, but we have to say when and how much in advance, and make cancelling as easy as signing up was."

The current design doesn't meet what consumer protection asks for.

All of this landed on Pagedeck in one week, when the team moved free users onto paid team plans and added card payments. Grace had registered the business at founding but had never filed the online sales report, and the processor's review asked for that number, which cost four days. Mia spent those four days writing down what the payment screen owed the customer: who is selling, how much leaves the account and when, and where cancelling lives.

In Noa's original design, cancelling sat three levels into settings. After the list, it moved to the first line of the billing screen, and Theo wired up an email that goes out three days before a trial converts. Ravi's landing page copy got the same pass. A line calling Pagedeck the number one collaboration tool came out, because no survey existed to point at, and a count of how many teams were on the product went in instead.

The most common belief is that none of this applies to a small company. Enforcement stories in the news are about large ones, and a ten-person team can't plausibly cover the whole surface, so the assumption is reasonable. But filing and disclosure duties have no revenue threshold, and most investigations start from a single user complaint rather than a sweep. Left alone, what arrives first isn't a fine — it's a blocked payment method or a rejected app review. Processors and app stores check these items as a condition of their own contracts, so one missing document stops revenue that day, and getting it restored runs on their review queue rather than on your launch calendar.

The other belief is that it can wait for a legal hire. It looks like specialist territory, and deferring specialist work to a specialist sounds safe. Most of what regulation asks for, though, lands in screens and processes rather than documents. What to show before taking money, where to put the cancel button, when the reminder email goes out — decided while building, each is half a day. Decided after launch, the payment flow gets rebuilt, every customer already charged has to be notified, and the team spends a sprint on work that produces nothing a user would notice. The first month of a new legal hire usually goes to unwinding exactly this backlog, and the longer the product has been selling, the more of it there is.