Amaru Group Ltd.

Amaru Group Ltd. We help non-technical founders turn ideas into launch-ready products. https://www.amarugroup.com/portfolio

Discover some of our recent custom software development solutions we have delivered that enable our clients to achieve unique business goals.

21/05/2026
09/04/2026

08/04/2026

08/04/2026

Your Startup Doesn't Need More Features. It Needs Better Onboarding.---Your sign-ups are growing. People are finding you...
07/04/2026

Your Startup Doesn't Need More Features. It Needs Better Onboarding.

---

Your sign-ups are growing. People are finding your product. The landing page is converting. The ads are working. Users are clicking "Create Account."

And then they vanish.

Not after a week. Not after a day. Within minutes.

They signed up, looked around, didn't understand what to do next — and closed the tab. Forever.

You respond the way most founders respond: by building more features. A dashboard. An export tool. An integration. A notification system. Surely if the product did more, users would stay.

But the users who left didn't leave because the product was missing something. They left because they never found the value that was already there.

**Your product doesn't have a feature problem. It has an onboarding problem. And it's the most expensive leak in your entire funnel.**

Here's what the data says:

→ 63% of users decide whether to keep using a product within the first 5 minutes — before they've explored a single advanced feature
→ 75% of new sign-ups never complete onboarding and never return to the product
→ Users who reach their "aha moment" in the first session have 3× higher 30-day retention than those who don't
→ Improving onboarding completion by just 10% typically increases overall revenue by 15–25%
→ The average SaaS product loses more users in onboarding than at any other point in the customer lifecycle — more than churn, more than competitors, more than pricing objections
→ Yet only 12% of startups invest meaningful resources in onboarding design before launch

**What is onboarding, really?**

Most founders think onboarding means: sign-up form, email verification, welcome screen, done.

That's not onboarding. That's registration. Registration gets someone into the building. Onboarding shows them why they should stay.

Real onboarding is the entire experience between "I just created an account" and "I understand why this product is valuable to me." It's the bridge between curiosity and commitment. Between sign-up and habit.

And for most startups, that bridge is missing entirely.

**The "empty room" problem:**

Here's what most products look like to a new user:

They sign up. They land on a dashboard. The dashboard is empty. There are tabs they don't understand. Buttons that don't mean anything to them yet. A sidebar with 8 menu items, none of which obviously answer the question every new user is silently asking:

"What do I do now?"

This is the empty room problem. You've invited someone to a party, but when they walk in, the room is dark, the music hasn't started, and nobody is there to greet them.

They look around for 10 seconds. Then they leave.

It doesn't matter how good the party gets two hours in. They'll never know. Because the first 30 seconds told them everything they needed to decide.

**Why founders underinvest in onboarding:**

**Reason 1: It's not a feature.**

Onboarding doesn't show up on a competitive feature comparison chart. It's not something you demo to investors. It doesn't make a good screenshot for Product Hunt. Founders love building features because features feel like progress. Onboarding feels like... polish.

But here's the math: a product with 10 features and 20% onboarding completion is a product where 80% of users never experience any of those features. A product with 5 features and 80% onboarding completion is a product where the vast majority of users engage with everything you've built.

Features you build don't matter if users never reach them.

**Reason 2: The founder knows the product too well.**

You've been staring at your product for months. You know every screen, every button, every flow. The navigation feels obvious — to you. The value proposition is clear — to you. The empty dashboard doesn't feel intimidating — to you.

But you are the worst possible tester of your own onboarding. Because you can never experience your product for the first time again. You've lost the ability to see it through a beginner's eyes.

This is why the most successful products in the world obsess over onboarding: because they know that the experience of a first-time user is fundamentally different from the experience of the person who built it.

**Reason 3: Founders assume users will figure it out.**

"The product is intuitive enough. Users will explore."

No, they won't.

Users are busy. They're distracted. They have 14 other tabs open. They gave your product 60 seconds of attention — maybe — and if those 60 seconds didn't deliver a clear reason to stay, they're gone.

The expectation that users will "explore" and "discover" the value on their own is the single most expensive assumption in product development. Because it treats user attention as infinite. It isn't. It's the scarcest resource in the world.

**The five onboarding failures that kill retention:**

**Failure #1: Asking for too much before delivering any value.**

Your sign-up form has 8 fields. Your onboarding flow requires profile completion, team setup, integration configuration, and preference selection — all before the user sees a single screen of value.

Every step between "create account" and "experience value" is a step where users drop off. The more you ask before delivering, the fewer users make it through.

The best products flip this: deliver value first, then ask for information. Let users experience the core value before requesting their company name, phone number, or billing address. Front-load the reward. Back-load the ask.

**Failure #2: No clear first action.**

A new user lands in the product. There are 6 things they could do. None of them are highlighted, suggested, or guided. The product says: "Here are your tools. Good luck."

New users don't want options. They want direction. They want to know: "What is the ONE thing I should do right now to get value from this product?"

The best onboarding experiences answer this question within 3 seconds of the user's first interaction. A single, prominent call-to-action. "Create your first project." "Import your data." "Send your first invoice." One action. One clear next step.

**Failure #3: Explaining what the product does instead of showing it.**

Product tours that consist of 12 tooltip bubbles explaining what every button does. Welcome modals with paragraphs of text. Video tutorials that the user has to watch before doing anything.

Nobody reads tooltips. Nobody watches tutorials during their first session. Nobody wants to be told what a product does — they want to experience what it does.

The best onboarding is experiential, not informational. It puts the user inside a real task immediately. If your product manages invoices, the first experience should be creating an invoice — not reading about how invoices work.

Show, don't tell. Always.

**Failure #4: No empty state design.**

The user's dashboard has zero data. Their project list is blank. Their inbox is empty. And the product shows them... nothing. A blank page with a plus button in the corner.

Empty states are the most overlooked onboarding opportunity in product design. Because every new user sees them. Every single one. And what you put in that empty space determines whether the user takes their first meaningful action — or bounces.

Great empty states do three things: they explain what this area will show once populated, they tell the user exactly how to populate it, and they make taking that first action feel effortless. "No invoices yet. Create your first one — it takes 30 seconds." That's an empty state that converts. A blank page with a "+" icon is not.

**Failure #5: No definition of "done."**

The user completes the onboarding steps. They created an account, set up their profile, maybe even performed one action. Then... what?

There's no congratulation. No summary. No confirmation that they've done the right thing. No suggestion for what comes next. The product just... goes quiet.

Great onboarding ends with a clear moment of completion. A celebration screen. A summary of what they've set up. A recommendation for their next session. This moment transitions the user from "onboarding" to "using" — and without it, they don't know if they're done, if they missed something, or if there's more they should do.

The transition from onboarding to regular use is a design moment that most products ignore entirely.

**The "aha moment" — and why finding yours is the most important thing you'll do:**

Every successful product has an "aha moment" — the specific moment when a user first experiences the core value.

For Dropbox, it's seeing a file appear on a second device. For Slack, it's receiving a message from a colleague in a channel. For Uber, it's watching a car approach on the map. For Canva, it's downloading a design that looks professional.

Your product has one too. And the entire purpose of onboarding is to get users to that moment as fast as possible.

Here's how to find yours:

**Step 1:** Look at your retained users — the ones who stuck around for 30+ days. What did they all do in their first session? What action did they take that non-retained users didn't?

**Step 2:** Talk to retained users. Ask: "When did you first realize this product was useful?" Their answer is your aha moment — described in their words, not yours.

**Step 3:** Measure the time from sign-up to that moment. That's your "time to value." Everything in your onboarding should be designed to shrink it.

**Step 4:** Remove every step, screen, and interaction between sign-up and the aha moment that isn't absolutely necessary. Every additional step is friction. Every friction point loses users.

**The onboarding audit — how to diagnose your problem:**

Before you redesign anything, measure what you have:

✔ **Onboarding completion rate.** What percentage of users who create an account complete your onboarding flow? If it's below 50%, you have a critical problem.

✔ **Time to value.** How long does it take the average new user to reach the aha moment? If it's more than 5 minutes, you're losing the majority of potential retained users.

✔ **Step-by-step drop-off.** Where in the onboarding flow do users abandon? The step with the highest drop-off is your highest-priority fix.

✔ **Day 1 return rate.** What percentage of users who sign up today come back tomorrow? If it's below 30%, the first session isn't delivering enough value to create a habit.

✔ **Activation rate.** What percentage of users perform the key action that predicts long-term retention? If it's below 40%, onboarding isn't driving users to the aha moment.

These five metrics tell you more about your product's health than any feature usage dashboard ever will. And they should be the first thing you look at every morning.

**The onboarding redesign framework:**

**Phase 1: Map the current experience.** (1 week)

Sign up for your own product with a fresh account. Record the entire experience. Note every question, every confusion point, every moment of friction. Then watch 5 real users do the same thing. Document everything.

**Phase 2: Define the aha moment.** (1 week)

Analyze retained vs. churned users. Identify the key action that predicts retention. Define your aha moment in a single sentence: "The user experiences value when they ______."

**Phase 3: Design the shortest path.** (2 weeks)

Map the minimum number of steps between sign-up and the aha moment. Cut everything that isn't on that critical path. Move optional steps to after the aha moment. Front-load value. Back-load complexity.

**Phase 4: Build and test.** (2–4 weeks)

Implement the new onboarding. Measure completion rates, time to value, and activation rate. A/B test against the old flow if possible. Watch 10 new users go through it. Iterate based on what you see.

**Phase 5: Optimize continuously.** (Ongoing)

Onboarding is never done. As your product evolves, your onboarding must evolve with it. Review your onboarding metrics monthly. Run user tests quarterly. Treat it as a living system — not a set-it-and-forget-it checklist.

**The ROI of onboarding investment:**

This isn't a soft, feel-good investment. It's the highest-leverage growth work a startup can do.

Consider: if you currently convert 20% of sign-ups to active users, and you improve that to 40%, you've doubled your effective user base — without spending a single additional dollar on acquisition.

Every dollar you spend on marketing brings you a sign-up. What happens between that sign-up and the aha moment determines whether that dollar was an investment or a waste. Onboarding is the multiplier that determines the return on every growth dollar you spend.

A 2× improvement in onboarding completion is equivalent to 2× your marketing budget — for free.

No feature will ever give you that return.

**Examples of onboarding done right:**

The products that dominate their markets all share one trait: they're obsessive about the first-time experience.

Notion drops you into a pre-built workspace with example content — you see immediately what the product can do, without building anything yourself.

Duolingo puts you into a lesson within 30 seconds of installing the app — before asking you to create an account. Value first, registration second.

Figma lets you start designing in a shared file within moments — no installation, no configuration, no setup.

Linear pre-populates your workspace with sample issues and views — so the product looks useful before you've added any real data.

Every one of these products made a deliberate decision: the first experience matters more than the feature list. And every one of them wins because of it.

**At Amaru Group, onboarding isn't an afterthought — it's a core part of every MVP we build.**

We've watched too many startups spend months building features that users never discover because the onboarding fails. We take the opposite approach: design the path to value first, then build the features that path leads to.

Here's what we offer:

✔ Onboarding audits — we measure your current onboarding metrics, map the user flow, identify drop-off points, and prioritize fixes by impact
✔ Aha moment identification — we analyze your user data and conduct user interviews to find the specific action that predicts retention
✔ Onboarding flow redesign — complete re-architecture of the first-time experience, designed to minimize time to value and maximize activation
✔ Empty state design — turning every blank screen into an onboarding opportunity that drives the user's first meaningful action
✔ Progressive onboarding implementation — systems that reveal complexity gradually, matching the user's growing familiarity with the product
✔ Onboarding analytics setup — dashboards that track completion rates, drop-off points, time to value, and activation rate in real time
✔ A/B testing infrastructure — tools and frameworks to continuously optimize the onboarding experience based on real user behavior

Because the fastest way to grow isn't to get more users in the door. It's to keep the ones you already have from walking out.

**If you're currently:**

– Getting sign-ups but watching users disappear before engaging
– Wondering why users aren't discovering the features you built for them
– Building more features to improve retention instead of fixing the first experience
– Running paid acquisition campaigns without tracking what happens after sign-up
– Noticing that users who do stick around love the product — but most don't get that far
– Unable to define what your product's "aha moment" is
– Seeing high Day 1 churn that no amount of email sequences can fix

Message us.

We'll do an onboarding audit — a data-driven, user-tested evaluation of where your product is losing users in the first session and exactly what to fix first.

No pitch. No pressure. Just 15 years of building products that don't just get sign-ups — they keep them.

---

Your Pricing Is Wrong. And It's Costing You More Than Revenue.---There's a conversation we have with nearly every founde...
03/04/2026

Your Pricing Is Wrong. And It's Costing You More Than Revenue.

---

There's a conversation we have with nearly every founder we work with. It happens after the MVP is built, sometimes after launch, sometimes months into a product that has real users.

We ask: "What are you charging?"

And the answer falls into one of three categories:

"Nothing yet. We want to get users first."
"$9/month. We wanted to keep it accessible."
"We have a free plan with unlimited everything. Paid starts at $5."

All three answers sound reasonable. All three are slowly killing the startup.

**Pricing isn't a marketing decision you make later. It's a product decision you make now. And getting it wrong has consequences that go far beyond revenue.**

Here's what we see play out — again and again:

→ 80% of startups underprice their product at launch, and most never fully recover because they've anchored their market's expectations too low
→ The average freemium product converts only 2–5% of free users to paid — meaning 95–98% of the users you're serving, supporting, and scaling for generate zero revenue
→ Raising prices on existing customers is 10× harder psychologically and operationally than setting the right price from day one
→ 54% of startups that failed never tested whether anyone would actually pay for what they built — they assumed demand and built on hope
→ Startups that charge from day one reach profitability 2× faster than those that delay monetization
→ Founders who test pricing during the MVP phase report 3× more useful feedback than those who only test the product

**The three pricing mistakes that kill startups:**

**Mistake #1: Giving it away for free — indefinitely.**

"We'll monetize later."

This is the most dangerous sentence in startup finance. Because "later" almost never comes the way you imagine.

Here's what actually happens:

You launch for free. Users sign up. Some of them love the product. You celebrate the growth. You show the numbers to investors. Everything looks great — on the surface.

But underneath, the economics are brutal. Every user costs you money — in server costs, support time, bug fixes, and infrastructure. And the more users you get, the more it costs. You're scaling your expenses while your revenue stays at zero.

Then the day comes to turn on pricing. And you discover something painful:

The users who signed up for a free product are not the same audience as people who will pay for a product. Free attracts everyone — including people who would never pay at any price. The users you've been celebrating? A large percentage of them aren't customers. They're freeloaders who will leave the moment you ask for a credit card.

And the users who would have paid? Many of them already formed a perception of your product as "the free tool." Changing that perception is exponentially harder than setting the right expectation from the start.

The cruelest part: free users generate the most support tickets, the most feature requests, and the most complaints. They cost the most and contribute the least. You've been optimizing your product for the wrong audience.

**When free makes sense:**

Free is a valid strategy — in specific contexts. A free tier works when it serves as a distribution engine (like Dropbox, where free users invited paying users). A free trial works when the product's value is hard to explain but easy to experience. A limited free plan works when it gives enough value to demonstrate the product but withholds enough to motivate upgrading.

But free as a default — free because you're scared to charge, free because you don't know what to charge, free because you want to "get users first" — is not a strategy. It's avoidance.

**Mistake #2: Underpricing out of fear.**

"$9/month. We didn't want to scare people away."

This is the pricing equivalent of apologizing for your product before anyone uses it. And it communicates something you don't intend: that your product isn't worth much.

Here's what underpricing actually costs you:

**You attract the wrong customers.** Price is a filter. Low prices attract price-sensitive buyers — the people most likely to churn, most likely to complain, and least likely to become advocates. Higher prices attract serious buyers — people who have a real problem, value a real solution, and will stick around because the product delivers real ROI.

**You can't afford to serve them well.** At $9/month, you need hundreds of paying customers to cover a single developer's salary. At $49/month, you need far fewer. At $199/month, you can invest in support, onboarding, and product quality that create a genuinely better experience. Low prices force you to cut corners on everything that matters.

**You signal low value.** Whether we like it or not, price is a proxy for quality. A $9/month project management tool sits in a different mental category than a $49/month one — even if the features are identical. Buyers use price to make quality judgments, especially when they can't evaluate the product deeply before purchasing.

**You leave money on the table — permanently.** Every founder we've worked with who tested higher prices was surprised by the result. The pushback they feared almost never materialized. The conversion rate barely changed. And the revenue per customer jumped dramatically. The most common reaction: "I wish I had charged this from the start."

**You make unit economics impossible.** If your customer acquisition cost is $30 and your customer pays $9/month with an average retention of 4 months, your LTV is $36. You're making $6 per customer. That's not a business. That's a rounding error. The same product at $29/month with the same retention generates $116 LTV — and suddenly the business works.

**Mistake #3: Pricing by cost instead of value.**

"It costs us $3 per user to host, so we charge $12 — that's a 4× margin."

Cost-plus pricing makes sense for manufacturing. It makes no sense for software.

Your price should have nothing to do with what the product costs you to deliver. It should be based entirely on how much value the product creates for the user.

If your invoicing tool saves a freelancer 5 hours per month, and that freelancer's time is worth $75/hour, you're creating $375/month in value. Charging $12 for that isn't "affordable." It's leaving $350 on the table — money that could fund your business, improve your product, and serve your customers better.

The best SaaS companies in the world price based on a simple formula: charge 10–20% of the value the product creates. If you save someone $375/month, $49–$75/month is a no-brainer for them and a sustainable business for you.

**Why founders get pricing wrong — the psychology behind it:**

Pricing isn't a math problem. It's an emotional one. And the emotions that drive founders to underprice are predictable:

**Imposter syndrome.** "Who am I to charge $49 for this? It's just an MVP." This feeling has nothing to do with the product's value and everything to do with the founder's confidence. Your product doesn't need to be perfect to be worth paying for. It needs to solve a real problem — and if it does, the price should reflect the value of that solution, not the founder's insecurity.

**Fear of rejection.** "If I charge too much, nobody will sign up." The fear of hearing "no" to a price is paralyzing. But here's the truth: hearing "no" to a price is one of the most valuable pieces of data you can collect. It tells you where the value ceiling is. Hearing "yes" to a price that's too low tells you nothing.

**Comparison anchoring.** "My competitor charges $15, so I should charge $12." Competing on price is the weakest competitive position imaginable. It tells the market that the only reason to choose you over them is that you're cheaper — not better, not different, not more valuable. The moment they lower their price, you lose.

**Guilt.** "My users are small businesses and freelancers. I don't want to charge them too much." This sounds compassionate. But consider: if you underprice, you can't afford to build a great product. Your support suffers. Your development slows. Your business becomes unsustainable. And the people you're trying to help lose the product entirely because the company folded. Charging a fair price isn't exploitative. It's how you stay alive to serve them.

**How to price your product — a framework for founders:**

**Step 1: Quantify the value you create.**

Talk to 10 users. Ask them: "What does this problem cost you today — in time, money, or missed opportunities?" If your product saves them 10 hours a month and their time is worth $50/hour, you're creating $500/month in value. Write that number down. It's your pricing ceiling.

**Step 2: Set your price at 10–20% of the value.**

If you create $500/month in value, price between $50–$100/month. This feels like an obvious deal for the customer and creates sustainable economics for your business. If you're unsure, start at 15%.

**Step 3: Test the price before you build the full product.**

Put the price on your landing page. See if people still sign up. Run a pre-sale. Offer early access at the planned price. If people pay — you've validated both the product and the price in one step.

If nobody pays, the problem isn't the price. It's the value proposition. Fix that before you build anything.

**Step 4: Start higher than you think.**

You can always lower a price. Raising a price is agonizing.

If you're unsure between $29 and $49, start at $49. If conversion tanks, drop to $39. If it doesn't, you just found your price — and you'll never know how much money you would have left on the table at $29.

The founders who start high and adjust down collect data. The founders who start low and try to go up face resistance, churn, and public complaints.

**Step 5: Use pricing as a validation tool.**

Here's something most founders miss: price is the strongest signal of real demand.

Anyone will say "That's interesting" about a free product. But when you ask someone to pay — even $10 — you learn something fundamentally different about whether they value what you've built.

A product with 1,000 free users and 0 paying customers has not been validated. A product with 50 paying customers has. The second product is further along than the first — despite having fewer users.

Price is the ultimate bu****it filter. Use it early.

**Step 6: Build your pricing into the product experience.**

Your pricing page isn't a footnote — it's one of the most important screens in your entire product. It communicates what you offer, who it's for, and what it's worth. It should be designed with the same care as your onboarding flow.

Great pricing pages do three things: they make the value obvious, they make the decision simple, and they create urgency without being manipulative. Bad pricing pages bury the price, overload users with tiers, or force them to "contact sales" for something that should be self-serve.

**The freemium trap — a special warning:**

Freemium can be a powerful model. It can also be a slow death.

The model works when free users drive paid growth — through invitations, collaboration features, or network effects. Slack's freemium model works because teams that start free inevitably grow into paid as they add members and hit limits.

The model fails when free users are just... free. When they use the product, consume resources, and never convert. When the free tier is so generous that there's no reason to upgrade. When the gap between free and paid is a hard wall instead of a natural progression.

Here's the test: if you removed your free tier tomorrow, would your business collapse — or would it clarify?

If most of your value is delivered in the free tier, your paid tier isn't compelling enough. If 97% of your users never upgrade, you're not running a freemium model — you're running a charity with a tip jar.

**The pricing conversation most founders avoid — and shouldn't:**

If you're uncomfortable talking about pricing, ask yourself: would you work for free?

You spent months building this product. You invested your savings, your time, your relationships. The people who use it get real value from it. Why would you not ask for fair compensation?

Pricing isn't greed. Pricing is how products survive. It's how companies hire better engineers, provide better support, and build better features. It's how a startup becomes a business.

The founders who price with confidence build sustainable companies. The founders who price with apology build products that eventually disappear — not because nobody wanted them, but because nobody paid enough to keep them alive.

**At Amaru Group, we help founders build products that are designed to monetize — not products that defer the hardest question until the runway runs out.**

Pricing isn't something we think about after the MVP is built. It's something we think about during the scoping phase — because pricing decisions affect product decisions.

What features go in the free tier vs. paid? Where do the natural upgrade triggers live in the user flow? How does the product communicate value before asking for money? What does the pricing page look like? How does the checkout experience reduce friction?

These aren't afterthoughts. They're design decisions. And they need to be made early.

Here's what we offer:

✔ Pricing strategy workshops — we help you quantify the value you create, identify your pricing ceiling, and choose a model that matches your product and audience
✔ Value-based pricing analysis — moving you from "what should we charge?" to "what is this worth to our customers?" using real user data
✔ Freemium architecture design — if freemium is right for your product, we design the free-to-paid boundary so conversion is a natural outcome, not a hard sell
✔ Pricing page UX design — building pricing experiences that communicate value clearly and reduce decision friction
✔ Monetization-ready MVP scoping — building products with pricing integration from day one, including payment flows, trial logic, and upgrade triggers
✔ Price testing frameworks — A/B testing infrastructure and methodologies to find your optimal price point before committing

Because a great product at the wrong price isn't a business. It's a hobby that costs money.

**If you're currently:**

– Giving your product away for free and telling yourself you'll monetize later
– Charging $9/month and wondering why the business doesn't work
– Afraid to raise prices because you think users will leave
– Running a freemium model with a 1–2% conversion rate
– Building an MVP and haven't thought about pricing yet
– Getting sign-ups but no revenue — and not sure what the gap means
– Comparing your price to competitors instead of to the value you create
– Uncomfortable talking about money with your users

Message us.

We'll help you figure out what your product is worth, what your customers will pay, and how to build a pricing strategy that turns users into revenue — without apologizing for the ask.

No pitch. No pressure. Just 15 years of building products that people use — and pay for.

---

Address

Kemp House, 160 City Road
London
EC1V2NX

Alerts

Be the first to know and let us send you an email when Amaru Group Ltd. posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Amaru Group Ltd.:

Shortcuts

Share