Hello everyone!

I think the math most freelancers use is wrong. They take a salary number, divide by 2,080, and call it their rate. That ignores many key factors, such as self-employment tax (15.3%), state income tax, unpaid hours, health insurance, and expenses.

I just want to say thank you.
To the people who have quietly supported Okiela, shared feedback, opened doors, and gave this small product a chance to be seen by more people.
It means a lot.
Okiela is still early.
Still small.
Still being built by one solo founder from Vietnam, with an FP&A finance background, trying to turn a very real ecommerce pain into something simple enough for operators to use.
The problem I keep coming back to is this:
many ecommerce operators can see revenue,
orders,
ads,
ROAS,
refunds,
and channel performance
but still struggle to answer one simple question:
after all the costs, what is actually left?
That is what Okiela is trying to make clearer.
Not for finance experts only.
Not for people who love spreadsheets.
Not for technical teams only.
But for real ecommerce operators who need to make practical decisions faster:
which product is really profitable,
which cost is eating margin,
which channel looks good but leaves little behind,
and where the business should focus next.
Recently, I also had the chance to share some Okiela materials in an AI & Finance community, including how the Profit Waterfall works in a real ecommerce case.
Small moments like that matter to me.
Because every piece of feedback, even the small ones, helps me see what Okiela still needs to improve.
If something is not clear enough, I want to know.
If a calculation does not feel right, I want to fix it.
If the insight is not practical enough, I want to make it better.
I know building solo is slower.
But I also believe slow can still be strong if the direction is right and the product keeps getting closer to the real pain.
The goal is simple:
help ecommerce operators understand true profit faster, without needing advanced Excel skills, finance knowledge, or technical setup.
Still learning.
Still listening.
Still building.
And genuinely thankful for everyone supporting Okiela along the way
#buildinpublic #ecommerce #shopify #shopee #profitability #saas #founderjourney #Okiela

A few weeks ago I was considering moving to another city in Germany. I expected the hard part to be making the decision. Instead, the hard part was finding reliable information.

Most resources I found were either:

• SEO-driven relocation content

• subjective opinions on forums and Reddit

• rankings with questionable methodologies

• official datasets scattered across dozens of government websites

Turning Chat Chaos into Context

Using AI daily, I kept hitting the same problem:

Great conversations impossible to find or reuse later.

We just launched a tool that came out of our own daily struggles with local SEO. For years, we've been using clunky VPNs to check rankings in different cities, and it always felt like overkill. So we built something simpler: a location spoofing tool for Google searches. No VPN needed, just enter a city and see the search results like you're there. It's perfect for agencies, freelancers, or anyone managing local listings. We're excited to share it with the community and hear what you think.

I'm a solo founder, and I built Shield after watching too many people lose everything to a single click. Not to some sophisticated hack to a malicious approve they couldn't read.

Here's the problem: a signature request today is a wall of hex. Your wallet shows it to you but never tells you what it actually does. So people hit "Confirm" and hope for the best.

Shield steps in before you sign:

Every time I wanted to tweak a margin or color during development, I did the same thing:

I m building SealedPacket, a local-first encrypted packet app for sensitive files and messages.

The idea is simple:

Choose text or a file

Encrypt it locally in the browser

Hello everyone. Welcome back to my siterows.com series.
Quick reminder of what this app does: Allows you to scrape web content with SQL, like you would query a DB. Creating a FREE account unlocks automation features and higher usage limits.
Today's question: "What if I'm using something like Selenium to navigate somewhere (perhaps logging into a site), and then I want to query the page?"
In order to accommodate this, I just added the ability to pass a raw HTML string to the /Scrape API endpoint, instead of a URL. Below is a Python example/response that demonstrates this new feature, and I'm also saving all examples in this GitHub repo: github.com/sgt-oz/SiteRows.
Basically here is what's happening:
* Function fetch_logged_in_html() uses Selenium to log into a site and return the home page's HTML string
* That string is passed to the /Scrape API endpoint. Instead of the payload being: {"url": "mywebpage.com"}, you just pass:
{"html": "<body><a href=...>.....</body>"}
....and that's pretty much it. SiteRows queries your HTML and gets results as if you passed a page URL to it.
Thanks, everyone. Please don't hesitate to reach out with any questions or feedback.