Little Something · Working document · November 2026

Business Model

Working document, November 2026. How the product reaches the market, how it makes money, what a gift costs and what the owner gains. Figures marked as estimates are my own assumptions, not vendor quotes.

Summary

Little Something launches as a standalone app owned by a bank, following the Tikkie model. The app keeps its own brand and works for customers of any Dutch bank. The bank holds the licence and moves the money, so there's no separate payment provider and no fixed minimums.

Individuals pay little or nothing, so the product can spread. The core experience, including every look and printing the card, stays free. Money comes from brand offers tied to what the gift is for and, later, a small giver fee. For the bank, the bigger gains are reach beyond its own customers, new accounts from receivers, and deposits waiting in gifts.

The current flow and designs stay as they are. They were designed for a standalone app, and this path keeps it standalone.

Launch paths considered

Why the chosen path:

• It fits the existing standalone designs and the personal, playful positioning.
• It removes the provider minimums that make standalone unit economics hard (see unit economics).
• Precedents point the same way: Tikkie and the other bank-owned apps below became national defaults.
• Trust is a launch problem for a new app holding money. A bank behind it helps without diluting the brand.

Reference case: Tikkie. ABN AMRO owns it, but anyone with a Dutch bank account can use it. People paying don't even need the app, and it reports over 10 million users. It's free for individuals, so ABN AMRO earns nothing directly from consumer Tikkies. It earns from:

• Business Tikkie: €7.50 a month including 20 paid Tikkies, then €0.15 to €0.25 per paid Tikkie depending on volume, excluding VAT, plus €0.10 per SMS. It mostly requires an ABN AMRO business account, and almost 40,000 businesses use it.
• Paid cashback and deposit refund services for companies.
• Brand campaigns and advertising inside the app.

The free consumer side is what makes the paid side valuable.

Sources: ABN AMRO Tikkie page, Tikkie FAQ, Tikkie business pricing, Bank.nl on how ABN AMRO earns from Tikkie

Precedents: bank-owned standalone apps

Tikkie isn't a one-off. Banks in several countries run separate apps with their own brands, and the ones that failed are as useful as the ones that worked.

What this means for Little Something:

1. Separate apps survive when they do a job the main banking app can't: reaching every bank's customers, or one emotional job with its own brand.
2. The biggest risk is the Zelle one. If gifting becomes a standard feature in every banking app, the defence is the experience: the reveal, the card and the money keeping its gift label.
3. There's a business model to copy: free for individuals, revenue from merchants, brands or non-customers.

Sources: Vipps MobilePay, TWINT, NatWest Rooster Money, DBS PayLah!, Zelle app shutdown, Finn, Bo

Revenue streams

Principle: the giver pays, never the receiver. Taking a fee out of the gift (the receiver opens €40 and finds €38) breaks the signal of care the product is built on.

1. Free at launch, and the core stays free. Every look and printing the card at home stay free for good, because the experience is what the product competes on. Premium looks could be tested later, but the added value is doubtful.
2. Brand offers tied to the gift's intent. A gift "for a camera" shows the receiver a discount at camera shops, and the product earns affiliate commission. The money stays fully flexible, so brands compete for attention instead of limiting where it can go.
3. Giver suggestions with store links (idea to test). When sending, the giver can add an optional suggestion: "You don't have to, but if you want, put it toward a jacket from your favourite store." The suggestion comes from the giver, so it keeps the effort with them, and a store link can earn a commission. Risk: with a store link it starts to feel like a gift card, so it stays optional and quiet.
4. Spending ideas after opening (idea to test). A prompt like "Ready to treat yourself?" opens a chat that suggests ways to spend the gift, using the note and what the gift is for as context. It has to appear on the opened gift or before "Move it to your bank", because once the money reaches the bank, purchases can't be tracked. Popular choices could be shown once there's data. Risk: it may feel pushy at the moment someone is enjoying the gift.
5. Small giver fee per gift. Framed like buying a greeting card, not a transfer fee. Switched on later, once givers come back to give again.
6. For the bank: indirect value (next section).

Later, not v1: interchange from a card (small, since EU consumer debit interchange is capped at 0.2%), and cross-border gifts with a currency margin (real revenue, but it pulls toward competing with Wise).

What the bank gains

Banks in the Netherlands make almost nothing on consumer transfers (SEPA is free for consumers, and so is Tikkie). So the case for the bank isn't fee revenue:

• New customers. Every receiver who isn't a customer has a reason to open an account. Compare new accounts per gift with the bank's usual cost of winning a customer. This is a bet to test: none of the bank-owned apps below publish how many accounts they brought in.
• Deposits. While money waits in a gift, the bank holds it and pays nothing on it. It can park that money at the European Central Bank (deposit rate 2.25% through 2026) or lend it out for more, and keeps the difference. Example, all assumptions: 10,000 gifts a month at €40, waiting two weeks on average, means about €200,000 held at any time, or roughly €4,500 a year. A supporting benefit, not a main one, and the money leaves when the receiver moves it to another bank.
• Engagement and brand. A warm, emotional moment from a bank that's otherwise a utility.
• Low cost to run. The bank already has the licence and rails, so internal transfers cost almost nothing. What's left is the cost to build and run the app.

What bank-owned standalone apps gave their banks

Public proof that these apps turned non-customers into bank customers is thin. What the banks did get:

• Tikkie (ABN AMRO): over 10 million users and €7.4 billion paid through it in 2024, plus tens of thousands of business users on the paid side. ABN AMRO talks about trust and reach, not account openings.
• Vipps (DNB): 1 million users within six months, open to anyone with a Norwegian bank account. Credited with new customers, purchase data and revenue of its own. Over 100 other banks later bought into it, so DNB ended up owning a national standard others paid to join.
• MobilePay (Danske Bank): the leading app in Denmark for customers and non-customers, which every other Danish bank eventually moved to. After the 2022 merger, Danske Bank owns 27.8% of Vipps MobilePay: strategic position and asset value rather than accounts.
• Rooster Money (NatWest): bought in 2021 with about 130,000 users, explicitly to reach younger customers early.

So the case to a bank is reach beyond its own customers, a younger audience, a brand people like and possibly an asset that gains value on its own. New accounts from receivers is a hypothesis to measure.

Sources: Tikkie 2024 (ABN AMRO), Tikkie Zakelijk (ABN AMRO), Vipps (Bundl), MobilePay (Wikipedia), Vipps MobilePay about, NatWest acquires RoosterMoney (FinTech Futures), ECB deposit rate 2026

Other owners considered

The case study leads with a bank-owned app and lists other possible owners. The evidence behind each:

• Money transfer apps (Paysend, Remitly). Occasions are a big reason people send money abroad: in a Remitly survey of 2,500+ senders, over a quarter send for holidays, weddings and celebrations, and 26% of December remittances go to special occasions (Remitly).
• Social or messaging apps launching payments. WeChat's 2014 digital red envelopes got over 5 million people to link bank cards in two days (Tech in Asia via Yahoo). X began rolling out X Money in the US in July 2026 (TechCrunch). In the West these features often struggle: Snapchat closed Snapcash in 2018 (TechCrunch), LINE Pay closed in Japan after merging into PayPay (LY Corporation), and WhatsApp's peer-to-peer payments run only in India and Brazil (Infobip).
• A feature inside a bank's app, or my own startup. Covered in Launch paths considered above.

Unit economics (estimates)

Why the standalone startup path is hard, using a €40 gift (the middle of the €15 to €100 range people described in interviews).

• A flat €1.99 giver fee roughly covers these costs, leaving about €0.50 to €1 per gift.
• Fixed costs are the real problem. Providers that publish prices start at about €3,000 a month (Swan) or £15,000 up front plus at least £4,000 a month (Griffin).
• Break-even example: about €6,000 a month in fixed costs ÷ about €0.75 per gift ≈ 8,000 gifts a month just to cover them.

Bank-owned path: provider fees and minimums disappear, and funding and payout costs drop to the bank's internal cost. The giver fee becomes optional, a positioning choice rather than a way to survive.

Comparison: Partiful never touches money, so it runs on hosting and messaging costs of a few cents per message. A product that holds money can't run that cheaply.

Sources: European BaaS pricing, Treezor review, BaaS costs and KYC prices, iDEAL fees compared

Considered and rejected

• Selling to companies. Work gifts go through a manager's budget as gifts, flowers or gift cards. In the Netherlands, cash given to employees is generally treated as salary, so companies prefer gifts in kind. The one place colleagues give money together, a leaving gift, needs group collection, which is out of scope.
• Earning from gifts nobody opens. EU e-money generally has to stay redeemable, there's no expiry by design, and profiting from forgotten gifts goes against the forgetting problem the product solves.
• Corporate accelerators (ABN AMRO with Techstars, Rabobank). Real programs, but they back founding teams with traction, and this year's themes are business infrastructure. A weak fit for a consumer gifting product at concept stage.

Growth paths for later

Group collection and pooling were never ruled out for good. For v1 I chose to focus on what nobody offers today, the personal gift experience, rather than on collecting money, which other products already do well. Once single gifts work, collecting for one person or one event is a natural next step.

Event gift mailbox

The idea. A host, for example a couple getting married, creates one gift mailbox for their event and shares a QR code or link on the invitation. Each guest who wants to give money makes their own gift through the usual flow: a photo (from the event, of the hosts, or a GIF or stock image from the app), a note and the money. Every gift lands in the host's mailbox, and the host sees who sent what, with their notes, ready for thank-yous.

Why it's interesting.

• A clearer reason to pay. The host gets real value (one link, every gift in one place, a list for thank-yous), so a fee for the host feels fair. Nothing is taken out of any gift.
• Growth. One event can bring 50 to 150 guests into the product, many of them customers of other banks. For a bank owner, that's reach and new-customer moments at a scale a single gift doesn't reach.
• It keeps the core. Each guest still makes a personal gift. It's many personal gifts landing in one place, not one pooled transfer.

What exists today. US wedding sites already offer cash funds. From their public pages:

So tracking who gave what is already solved. The gap is the guest's own expression: none of them let a guest make a gift with their own photo, note and reveal.

Open questions.

• Pricing: these sites charge between nothing and 2.5%, so a flat host fee has to be clearly worth more than free. A free basic mailbox with a paid tier for the host (event design, a keepsake page of all the gifts, a printed album) may be easier to justify.
• How comfortable people are with a money link on an invitation. In some cultures money at a wedding is expected; in others it can feel pushy. Worth asking in interviews.
• Whether European couples use these US sites, and what European wedding sites offer.
• The guest flow starts from the host's link, so event details could be pre-filled. A separate flow to design.
• The product rule "the giver pays, never the receiver" would become "nobody pays out of a gift".

Sources: Zola, Joy, The Knot

Open questions

• When to switch on the giver fee, at what level, and what has to be true first (enough repeat givers? a clear trust signal?).
• How much brand freedom a bank owner would really allow.
• Whether brand offers feel helpful or pushy to receivers. To test with users.
• How much ID checking a receiver from another bank can go through before it becomes friction.
• Whether Rooster Money's model (free for the bank's own customers, paid for others) fits gifting, where the receiver often banks elsewhere.
• How defensible the experience is if banks add simple gifting to their own apps.