One paying customer taught me not to confuse interest with revenue

I’m 17 and building a B2B product alone.

The first paying firm signed in June for NOK 20,000/year.

After that, another firm saw value in the product but used an accounting system I did not support. So basically I could not sell them.

Another possible firm had roughly 800 clients, but a proper demo was waiting on the same integration.

Those conversations matter, but they are not the same thing as a customer.

One signed customer is revenue.

A good sales conversation is information.

A requested integration is work, not a deal.

That distinction gets pretty important when you are the same person writing the code, doing the demos and deciding what to build next. A positive reaction can feel like progress while still being very far away from money.

The uncomfortable version of my situation was simple: one paying customer and an integration problem.

For people who have been through this stage, what do you count as real progress before revenue becomes repeatable?

reddit.com
u/Kevin00812 — 7 days ago
▲ 2 r/nextjs

How I handle hostname = market and path = language without /en leaking into canonicals

I have a public Next.js App Router site with two markets and one slightly annoying locale rule.

The .no host is the Norwegian market. It defaults to Norwegian, and /en is the English translation of that same Norwegian-market site.

The .com host is the international market and English only. Its canonical public URLs never include /en. Any .com/en URL permanently redirects to the equivalent clean path.

The important bit is that market-specific content follows the hostname, not the locale. So .no/en still needs Norwegian pricing, integrations, legal documents and availability, just in English.

I treat these as two separate values:

  • market comes from the hostname;
  • language comes from the path, subject to the host rules.

Shared country-neutral design and copy can follow the language. Pricing, integrations, availability and legal content follow the market.

The failure mode I want to avoid is letting “English” silently mean “international.” Then .no/en could show international commercial content while looking like a perfectly normal translation.

For anyone running this kind of setup in App Router: where do you draw the boundary between middleware/redirect logic, request-time market resolution and locale-aware components? I want the rule to stay obvious six months from now, not become ten pathname checks.

reddit.com
u/Kevin00812 — 7 days ago

The feature request that turned out to be the entire sale

I’m building a narrow SaaS for accounting firms, and one sales call changed how I think about integrations.

The workflow itself is simple: the firm has a transaction without a receipt or invoice, asks the client for it, follows up, gets the file and gets it back into the accounting workflow.

One firm saw the value in the product but used an accounting system I did not support.

So basically I could solve the problem and still not sell them the product.

Another possible firm had roughly 800 clients. A proper demo was waiting on the same integration.

That was when “do you integrate with our system?” stopped feeling like a normal feature request.

For some vertical SaaS products, the integration decides whether the customer can use the product at all.

I’m 17 and building alone, so that distinction matters. Every requested integration is work, but a requested integration is not a deal.

My first paying customer showed me somebody would pay for the problem. The other conversations showed me that the market on paper and the market I can actually serve are not the same thing.

For other vertical founders: what made you realize an integration was infrastructure, not just another feature?

reddit.com
u/Kevin00812 — 7 days ago

A missing integration killed my sales call. It changed how I’m launching BilagPilot internationally

I had one of those sales calls where the person sees value in the product, except for the part that makes actually using it impossible.

The firm needed Duett. I did not support Duett.

So a product they could see the point of became something they could not really move forward with.

Another possible firm had roughly 800 clients, but again the next step depended on the Duett integration. That made it hard to keep treating integrations as a technical checklist. In vertical B2B, sometimes the integration is what decides whether the customer can use the product at all.

I got my first paying firm in Norway on June 18 for NOK 20,000/year. Not huge traction, just one real customer.

BilagPilot does the same boring job it did before: find transactions without documentation, ask the client through a secure link, remind them, and get the file back into the accounting workflow.

Now I’m taking it international around QuickBooks Online and Xero.

I’m 17, solo, and very aware that one Norwegian sale does not mean the UK or Australia will work.

My current plan is UK first, Australia second, subject to validation. If you have taken a vertical SaaS into a second market, what broke first: the workflow, the integration, or the sales message?

reddit.com
u/Kevin00812 — 7 days ago

Hvor finner man gode norske B2B-møtebookere?

Jeg bygger et B2B-verktøy for norske regnskapsbyråer og skal teste mer telefonbasert salg fremover.

Jeg ser derfor etter måter å finne folk som faktisk er gode på cold calls og møtebooking i Norge. Ikke et stort salgsbyrå, men egt bare personer som kan salg og er villig til å prøve noe nytt.

Har dere noen tips til hvor man finner slike folk?

Tenker på ting som:

  • tidligere telefonselgere
  • freelance møtebookere
  • små salgsmiljøer
  • norske communities
  • steder hvor flinke selgere faktisk henger

Jeg har mest lyst til å finne én konkret person som kan teste dette sammen med meg, ikke bare kjøpe en dyr pakke fra et byrå.

PS: Hvis du kjenner noen personlig som er god på møtebooking, eller du selv kunne vært interessert i å teste noe sånt, send meg gjerne en DM 😄

reddit.com
u/Kevin00812 — 3 months ago

Etsy GPSR fields: 5 things I keep seeing sellers miss

I've been looking into GPSR for Etsy sellers, mostly because Etsy's fields make it feel like everything belongs in the listing itself.

The confusing part seems to be the split between:

- what needs to be visible to the buyer on the listing

- what should be kept in your own internal documentation

- what only matters if there is ever a safety issue, recall, complaint, or marketplace check

The five missing bits I keep seeing are:

  1. A clear manufacturer/responsible person name and contact route

  2. Product identifiers that match your own records

  3. Basic material/components notes

  4. A short safety-use note where it actually makes sense

  5. Internal notes on why you think the product is low risk

I just think a lot of the confusion comes from treating Etsy's listing fields as the whole compliance system, when they are probably only the public-facing part of it.

Are UK sellers here still shipping to the EU/NI, or have most of you paused it for newer listings?

reddit.com
u/Kevin00812 — 3 months ago