Most people treat pricing as a math problem. I used to think that too.

We had a product sitting at $230 on our homepage. Decent margins, nothing special. The real issue: distributors didn’t believe in it, and neither did the algorithm.

So I did something counterintuitive I raised the price to $399.

Before touching the number, I did the work:

•	Studied how competitors like Fiona and (G)I-DLE positioned their price hikes

•	Rewrote the product narrative as a “2026 version” same hardware, sharper story

•	Announced the increase publicly on Reddit and community forums before it happened

•	Briefed our distributor channel with a cost-justification doc, not an apology

What happened? Sales held. Distributor confidence went up because they saw we could command premium pricing. Amazon followed: $200 → $270, maintained volume.

The lesson I keep coming back to: price is a positioning signal, not just a revenue lever. When you raise price and the market accepts it, you’ve just told everyone what your product is worth.

Curious if others have navigated this on Amazon or DTC. What’s been your approach to pricing strategy when you’re a small team?

I recently ran a small experiment on a B2B campaign and wanted to share what actually worked.This is for a distributor / reseller type product.
Before changes, we were getting ~1 form submission per 100 visitors (~1%).After a few adjustments, we moved to ~5 submissions per 100 visitors (~5%).

1. Audience-message alignment (this was the biggest lever)

Before:

• Broad targeting
• Generic messaging

After:

• Narrowed down to a much more specific reseller persona
• Matched ad copy directly to their real concerns

People clicking already “felt understood”

2. Rebuilt the landing page around real questions (not marketing copy)

Instead of writing what we think matters, I pulled actual questions from existing distributors:

• “How does logistics work?”
• “What happens if customers request refunds?”
• “Do you provide marketing support?”
• “Is there proof this product actually sells?”
• “What kind of brand backing do you have?”

Then I turned the landing page into basically a FAQ-driven trust page

3. Added concrete proof instead of vague claims

Replaced generic claims with:

• Global presence (150+ countries)
• Distributor network
• Awards / credibility signals
• Real operational support (not just “we support partners”)

1. In B2B, conversion = risk reduction, not persuasion
2. Traffic quality matters, but message matching matters more
3. The best landing page copy is often already in your inbox / chats
4. If your ad promises X, your landing page must immediately confirm X

Start with this: “What are people already asking before they buy?”

Then answer that clearly on the page.

Curious how others structure B2B landing pages for reseller-type offers.

I recently ran a small experiment on a B2B campaign and wanted to share what actually worked.This is for a distributor / reseller type product.
Before changes, we were getting ~1 form submission per 100 visitors (~1%).After a few adjustments, we moved to ~5 submissions per 100 visitors (~5%).

1. Audience-message alignment (this was the biggest lever)

Before:

• Broad targeting
• Generic messaging

After:

• Narrowed down to a much more specific reseller persona
• Matched ad copy directly to their real concerns

People clicking already “felt understood”

2. Rebuilt the landing page around real questions (not marketing copy)

Instead of writing what we think matters, I pulled actual questions from existing distributors:

• “How does logistics work?”
• “What happens if customers request refunds?”
• “Do you provide marketing support?”
• “Is there proof this product actually sells?”
• “What kind of brand backing do you have?”

Then I turned the landing page into basically a FAQ-driven trust page

3. Added concrete proof instead of vague claims

Replaced generic claims with:

• Global presence (150+ countries)
• Distributor network
• Awards / credibility signals
• Real operational support (not just “we support partners”)

1. In B2B, conversion = risk reduction, not persuasion
2. Traffic quality matters, but message matching matters more
3. The best landing page copy is often already in your inbox / chats
4. If your ad promises X, your landing page must immediately confirm X

Start with this: “What are people already asking before they buy?”

Then answer that clearly on the page.

Curious how others structure B2B landing pages for reseller-type offers.

I didn't buy the Air for this. I bought it because I travel for work and wanted my Netflix to work abroad.

But a few weeks in, I noticed something weird in the network dashboard. One device was making outbound connections I didn't recognize. Checked the device list was the Ecobee thermostat that came with my apartment.

The destinations? Three different ad-tech domains and something from a data broker I'd actually heard of.

I don't own the thermostat. My landlord does. But it's sitting on my WiFi and apparently reporting... something... back to someone.

Blocked the domains through the Deeper console. Haven't noticed the thermostat stop working. Have noticed the connections have stopped.

I went through the rest of my network after that. The smart TV in the living room was calling home to 7 different endpoints on startup. My old Roomba, which I haven't used the app for in months, still pinged its servers twice a day.

None of this is secret. It's all in the privacy policies nobody reads. But seeing it as live traffic hits differently than reading a ToS.

Anyone else gone down this rabbit hole? Curious what people have found on their networks.

Spent about two hours this weekend going through every Google Maps setting, every linked Google Account control, every permission screen. I wanted to know exactly what I'd agreed to by using the app. What I found wasn't surprising, but seeing it laid out all at once was still unsettling.Here's what most people don't know.

The "Location History" toggle is a decoy.

This is the one setting everyone tells you to turn off. So I turned it off. Felt good about it. Then I kept reading. Buried in the confirmation pop-up, in smaller text, Google tells you: "location data may be saved as part of your activity on other Google services, like Search and Maps." Turning off Location History only stops Google from updating your Timeline. It does not stop Google from collecting your location. There's a separate setting, Web & App Activity, that keeps logging where you are. I only found out because I kept reading the fine print after clicking the toggle.

And it's not theoretical. After turning Location History off, Google Maps prompted me to rate a store I'd walked past, without me ever opening Maps or searching for that store. The app knew I was there. Through the other setting. The one I hadn't touched yet. So you turned off the visible setting, and Google kept tracking you. Through a different setting. That you didn't know existed.

Web & App Activity: the setting that does the actual tracking, hidden in plain sight.

This one covers your searches and activity across Google Search, Maps, Photos, News, YouTube, and Chrome. It stores location data. It can save activity even when you're offline or signed out. It's on by default. Here's the thing that got me: the description of Web & App Activity doesn't mention location tracking at all. And the description of Location History doesn't tell you that turning it off won't stop location tracking. You'd only know the full picture if you read both settings back to back and connected the dots yourself. The setting that actually tracks your location doesn't say "location." The setting called "Location History" doesn't stop location tracking. Everything is named to confuse you.

Wi-Fi Scanning: the one that keeps turning itself back on.

Settings > Location > Wi-Fi scanning. Turn it off. Come back tomorrow. It's on again. I've tested this multiple times. Any app that uses Google's location APIs seems to quietly re-enable it. Navigation on Google Maps stopped working for me without it, the app effectively held routing hostage until I turned it back on. And it's not just Maps: other apps that have nothing to do with navigation were also triggering the same behavior. You turn it off. Something turns it back on. You're never quite sure when it happened.

Incognito mode in Maps doesn't do what you think

I assumed Incognito in Maps was like Incognito in Chrome, a reasonable privacy mode. It's not. Google's own documentation says it plainly: Incognito mode in Maps doesn't affect how your activity is used or saved by your internet provider, other apps, voice search, or other Google services. Your ISP still sees your traffic. Your other Google apps still log your location. You just stop getting notifications and your searches don't save to your Maps history. That's it. It's a privacy theater feature.

What actually can't be turned off while using a Google account:

• Location inference via IP address on every search, regardless of your settings
• Basic travel data (routes, destinations, transport mode, visit frequency) collected through normal app use
• Emergency location services, which bypass your settings at the system level. Reasonable in principle, but it means there's no true off switch.

What you can actually do (ranked by impact):

1. Turn off both Location History and Web & App Activity, not just one
2. Disable Wi-Fi scanning and Bluetooth scanning in system settings, not just Maps
3. Set location permission to "only while using," never "always"
4. Use Incognito for sensitive searches, knowing it's partial, not complete
5. Switch to Apple Maps or OsmAnd. Not perfect, but neither is funded by profiling you.

The thing that got me wasn't that Google collects data. I assumed that going in. It was the architecture of confusion: settings named to sound like they do more than they do, fine print buried after you've already clicked confirm, defaults that are all on, and controls split across three different menus so that fixing one thing doesn't fix the thing. None of this is accidental design.

Has anyone found settings I missed? Curious if there's anything that actually works short of rooting.