Why NFC tag writing lives in Pro, not Plus

The ask came from everywhere

A salon owner in Manchester emailed: 'I want to repoint my cards at a new promotion without ordering new ones.' A property agent in London messaged through the app: 'Can I write to tags I've already got?' A freelancer who'd bought a batch of NFC cards three years ago asked if she could finally use them with TapTrust.

These weren't edge cases. They were people with real inventory, real costs, and a genuine frustration. They'd already bought physical cards. The idea that they could reprogram those cards themselves, on their phone, without waiting for us or ordering new stock, felt obvious to them. And honestly, it felt obvious to us too.

But obvious features aren't always obvious decisions.

The question wasn't whether to build it

It was where to put it. Plus tier felt like the natural home. At £2.99 a month or £24.99 a year, Plus was already our workhorse plan. Three profiles, unlimited reviews, unlimited shares. A customer jumping from Free got everything they needed to run a basic digital business card operation. The value was clear.

But NFC tag writing wasn't a basic feature. It was technical. It required explaining. It required a phone with NFC capability and understanding of how NFC protocols work. Most Plus customers never asked about it. They tapped their cards, collected reviews, shared the link. That was the job they hired us to do.

Pro tier, at £5.99 monthly or £49.99 yearly, was different. Those customers had already made a commitment. They wanted five profiles instead of three, which meant they were running multiple lines of business or managing teams. They'd seen real tap analytics. They'd watched location data come in. They understood the platform at a deeper level.

For them, the ability to write tags themselves wasn't a nice addition. It was infrastructure.

The cost wasn't just the code

We spent two weeks building NFC tag writing. That was the straightforward part: the API integration, the error handling, the permission requests on-device. What took longer was thinking through what could go wrong.

A customer writes a tag in our app, then loses their phone. Can they still access those tags from a different device? What happens if the tag gets corrupted? If someone accidentally writes over a tag that's already in use, how do we help them recover? If a team member writes a tag that breaks the account's profile architecture, what's the support burden?

These weren't hypothetical. We knew our customer base. A busy salon owner might hand her phone to a junior staff member to write tags. An estate agent might bulk-write cards before a property launch and get the configuration wrong. We'd need support resources, clear documentation, and defensive code to handle misuse.

That cost scales with the number of people using the feature. At Plus volume, it felt unsustainable. At Pro volume, it felt manageable. And it rewarded the customers who were already invested enough to pay for five profiles and real features we'd already built.

The real reason: product coherence

When you put a feature in the wrong tier, it doesn't just confuse pricing. It confuses the entire product story.

Plus tier says: 'You want a smart digital business card. Tap, review, done.' It's about simplicity and reach. The customer points people to their card, collects reviews, sees basic tap counts. Straightforward.

Pro tier says: 'You're running this seriously. You manage multiple profiles, you want to see where people are tapping you, you want control over your infrastructure, and you're willing to learn how the system works.' It's for people who've moved past 'just get it working' and into 'I want to own this.'

NFC tag writing belongs in that second story. It's a feature for someone who has inventory, who understands what a tag is, who plans to update cards multiple times. It's not for someone who just wants to tap and collect a review.

By placing it in Pro, we didn't gatekeep a useful feature. We put it where it made narrative sense, where the customer base had already shown they wanted to go deeper, and where we could support it without turning support into a blocker.

What we learned about listening

Here's what surprised us: when we announced NFC tag writing was coming to Pro, nobody complained. Not a single angry email. Customers on Plus said things like, 'Yeah, makes sense, maybe I'll upgrade when I need it,' or simply didn't care because they weren't trying to reprogram cards anyway.

The people who wanted tag writing weren't fighting for cheaper access. They were fighting for the feature to exist at all. They'd been staring at physical cards sitting in drawers, waiting for us to build something that would let them use them.

Once it existed in Pro, they upgraded. Some came from Free or Plus, but most were people who already understood the product and were just waiting for the next reason to go deeper. The feature didn't create a customer base. It served a customer base that was already reaching for something more.

That taught us to listen less to the volume of requests and more to the coherence of the request. Who's asking? What problem are they solving? What does that tell us about where they sit in their journey with the product?