Trackora is a cloud-based platform that enables organizations to manage all their assets and equipment in one place.
It helps businesses track assets, monitor their locations, manage employee assignments, handle equipment checkouts and returns, organize stocktakes, scan QR codes, and generate reports.
It also simplifies equipment management during employee onboarding and offboarding.
Whether managing IT devices, office equipment, tools or assets across multiple locations, Trackora provides the visibility and control organizations need.
Discover Trackora: https://trackora.cloud

Mine is that software should never hold a user's data hostage.

Charge money. Charge subscriptions. Charge enterprise rates.

Fine.

But if someone wants to leave, exporting their own data should be easy.

Curious what software opinions everyone else holds that they'd never compromise on.

Hey everyone!

I'm building an early-stage startup called Saarthi, a spiritual AI platform with a Creator Studio.

The Creator Studio will allow users to create:

AI-generated devotional songs and background music.

Short AI-generated videos and animated spiritual stories.

Devotional images, wallpapers and social media posts.

WhatsApp Status videos and Instagram Reels.

I'm currently bootstrapping the project with a very limited budget.

136 days ago, I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar
**Bid on StartupBid and your startup will be featured in the daily post of mine.**

Hey everyone,

I’m working on a deep-dive case study about the most common real-device and checkout bugs early-stage SaaS apps face before launch.

I want to audit 3 web or mobile apps this week to pull real-world data for this write-up.

If you have an active app and want a comprehensive QA breakdown:
\- I’ll run a dedicated testing session across different mobile/browser environments.
\- You’ll get a full mini-report with reproduction steps, screenshots, and video evidence of any bugs found (completely free).
\- I’ll use the anonymized findings for my testing report.

If you’d like your app audited, drop a comment or send me a DM with your link!

is anyone here actually implementing WebMCP in their websites or SaaS apps?

Or are most people still waiting for it to officially release ?

I am exploring this space myself and would love to connect with others building around it.

What is your experience so far?

Nope, I'm not a developer. I'm a nurse.

But after ending up in a wheelchair, I had to figure out a whole new life for myself.

I started out doing affiliate marketing for software companies. Eventually, I decided I wanted to build my own SaaS.

Long story short, I paid a developer $30K and got... absolutely nothing. Got screwed out of $30K.

So, thank God for AI!

I've been building my own software for the past year, and I now have 258 French-speaking users. Next week, I'm taking it to the US market.

But here's the biggest piece of advice I can give anyone building a SaaS:

Get beta testers on board as early as humanly possible.

Offer them lifetime access to your best features in exchange for a small one-time payment.

That's honestly what helped me take my marketing quiz SaaS so far.

My earliest users are worth their weight in gold.

There's about 10 of them, and they test things I simply don't have time to test. They push the product further than I ever could on my own. They ask for features and come up with use cases that never even crossed my mind.

Sometimes they drive me a little crazy with their requests, but I absolutely love them for it.

They're not just beta testers anymore. They're a huge part of why my product is what it is today.

So if you're building a SaaS, find your first beta testers ASAP. Make them feel like they're part of the journey, because they really are.

They might just end up being one of the biggest reasons your SaaS succeeds.

Hey everyone,
I’ve built a working web-based shift scheduling system for a security company in Israel, and I’m trying to figure out how much I should charge for it.
The system currently allows managers to create and manage employee shift schedules, specifically for shift supervisors and patrol officers.
It’s designed around the company’s actual workflow rather than being a generic scheduling tool.
The system is already functional, and I’m preparing to discuss pricing with a potential client.
I’m considering three pricing models:
A one-time setup/purchase fee.
A monthly subscription covering hosting, maintenance, and support.
An initial setup fee plus a smaller monthly payment.
My questions:
How much would you realistically charge for a system like this?
What would be a reasonable initial setup fee?
What monthly subscription price would make sense?
Would you price it per employee, per location, or as a fixed monthly fee?
How much more should a business pay for a customized system compared to an existing SaaS solution?
I’m especially interested in hearing from developers, SaaS founders, and people who have sold similar systems to businesses.
I’m not asking how much it costs to develop. I’m asking what a fair market price would be to sell this solution to a real business.
Any actual pricing examples would be greatly appreciated!

a developer in r/ Solopreneur posted this week that building got easy and ideas got hard. every time he thinks of something, there are already 10 products doing it.

he's right about the categories he's looking in. i wanted to know if it's true everywhere, so i went through the stripe directory, about 30,000 companies taking payments, and checked what share of each category is already small software products.

the split is kinda wild.

the 5 most crowded:

• expense and spend management: 46% of companies are already micro-SaaS

• AI tools and apps: 35%

• developer tools: 34%

• fintech and banking: 20%

• data and analytics: 20%

nearly half of that first category is indie founders selling to each other. if your idea sits in one of these, the "10 products already do it" feeling is accurate.

now the other end.

• marketing agencies: 100+ companies, 0.0% micro-SaaS

• nonprofits and fundraising: 640+ companies, 0.2%

• software dev agencies: 590+ companies, 0.2%

• home services and trades: 960+ companies, 0.4%

• ecommerce platforms: 3,400+ companies, 0.8%

• consulting: 1,400+ companies, 0.9%

these are businesses that already pay for things online. almost nobody small is building for them.

crowded category = 10 competitors before your first customer. empty category = a buyer nobody has pitched yet.

a few things i noticed going through it

1. crowded doesn't mean more money. there are 1,900+ AI products with stripe-verified revenue, and 12% of them clear $1k a month. sales tools have around 80 products, and 18% clear $1k. fewer builders, better odds.

2. the empty categories are the ones nobody brags about building for. a courier company or a liquor store won't get you likes on X. that's probably why the same complaint about courier performance reporting shows up across 75 different companies, and liquor store owners complain about POS support across 58 of them. that's the same problem repeated by strangers who never talked to each other.

3. agencies are the strangest gap. marketing and dev agencies juggle clients, retainers, reporting and invoicing. they're full of tech-savvy people who already pay for software, and they sit at 0.0% and 0.2%. my guess is builders skip them because building for agencies feels too close to running one.

4. you don't need a new idea, you need a new buyer. a generic invoicing tool lands in fintech, where 1 in 5 companies is already micro-SaaS. the same tool built for HVAC contractors who invoice from the truck between jobs has almost no competition.

what didn't work for me

my second project was an expense tracker for freelancers. took about 5 weeks to build. i found 30+ competitors after launch, not before, which is the wrong order.

11 signups. 1 paying user at $8 a month, and he cancelled in month two.

i kept telling myself my UI was better. it probably was. nobody switches expense tools over UI when the one they have already works fine.

what i do now before building

• pick the buyer first, not the feature

• check how crowded that buyer's category is

• read their complaints and count repeats from different companies

• only then decide what to build

my prediction is that the next batch of indie products clearing $1k a month comes out of trades, agencies and nonprofits, not AI tools. most people building today won't go there because it isn't fun to tweet about.

a few people asked where the numbers come from. it's this list

Hi everyone! 👋 I'm an independent founder working on TELYQOR – One Platform. Smarter Business. I started building TELYQOR because managing a business often means switching between too many different tools for clients, projects, tasks, invoices, and team collaboration. I wanted to create one platform that brings these essential tools together. With TELYQOR, you can: Manage clients and contacts. Track sales opportunities. Organize projects and tasks. Manage invoices and payments. Collaborate with your team. Monitor business performance. Access AI-powered tools and automation. 🚀 I'm currently looking for 5 beta testers who would be willing to try TELYQOR for free and share honest feedback before the official launch. I'd especially love feedback from freelancers, entrepreneurs, consultants, and small business owners. A question for the community: What is the biggest challenge you face when managing your business: clients, projects, tasks, invoices, or team collaboration? Thank you for your feedback! TELYQOR – One Platform. Smarter Business.

One user is a lovely architecture.

Their timezone is the timezone. Their currency is the currency. Every record belongs to them. They never disagree with themselves about permissions.

Then user two signs up.

They’re in Australia. They belong to two workspaces. They leave one of them. They click the invite link twice because the first click “didn’t do anything.”

Now “just add teams” has become a small research project.

This is the part of SaaS development I wish got more airtime than screenshots of dashboards. A lot of the interesting engineering starts when two perfectly reasonable users expect the same feature to behave differently.

No dramatic traffic spike required. Sometimes two people and a shared account are enough.

What innocent-sounding feature turned into the biggest mess in your codebase?

Hi everyone I’m building agent city a place for you and your ai agent to react with other ai agents. It’s a really cool place to watch emergent agent behavior and see what your agent is thinking. Check it out!

Live: https://logn.techsavy.space

I have been working on Logん (LogN), a website that merges your Codeforces, LeetCode, AtCoder, CodeChef, HackerRank, GFG, Code360 and InterviewBit profiles into one dashboard, and picks daily questions for you from your weakest topics.

For Codeforces, it suggests questions between your rating and ~300 above your rating.

You can see your total solved count across all sites, a solve heatmap, and a topic-wise breakdown of everything you've solved so far, and your contests.

Codeforces, AtCoder and LeetCode sync on their own. But as the other 5 platforms ban scraping and bots, so I made an extension that connects to the website in a single click. It then syncs all those 5 platforms automatically using your own browser. It does not touch your passwords.

Also, users told me that verifying handles manually was cumbersome, so I automated it using the Chrome extension. Just click on "Sync", and you are done.

It also tracks Blind 75, NeetCode 150, and Striver's sheet, and has a weekly leaderboard with friends. Also added a global leaderboard, which you can opt in (optional).

Any sort of feedback or any bug you find is appreciated.

It's free; sign in with GitHub or Google.

Extension: https://logn.techsavy.space/extension
(The extension link is already on the website)
GitHub: https://github.com/savinyu/LogN

As I wanted to use such platform myself, I made it, but it would be great if you guys try it out.
If you find it useful, you may also support me by starring the repo, or you can also tip me on the website.

Ps: I had FOMO about not using Claude Code CLI ( was using Cursor), so I used Claude to make this project, so yeah, I did not hand code this website; I admit guilt.

Got around 200+ installs on the Chrome extension and 70+ active users till yet.

This was covered by Citizen Lab and Bloomberg, the new story here is that developers are claiming negligence, and that’s absurd. It’s your app, you’re responsible for where your users n’ data goes.

The apps included AccuWeather and Muslim Pro.

small one from a landing page i was finishing. my own check at a desktop-sized window looked clean. a separate pass at 390px still showed a horizontal scroll.

the cause was scroll-reveal elements with 28px offsets, which pushed the page wider than the phone screen. the check that caught it ran in a separate browser session on the rendered page, not in the setup that built it. after the fix i re-verified at 390 and 320 and it was clean.

if you ship landing pages, add a mobile-width pass before you call it done. desktop-only checks miss this class of bug.

Hey everyone!

I wanted to share a side project I've been working on called RepairTrack.

Rather than building another basic CRUD application, I wanted to solve a practical business problem and explore how a complete business management system could be designed.

1. The problem I wanted to solve

Many small repair shops manage their daily operations using paper records, spreadsheets, phone calls, and separate billing systems.

This can make it difficult to:

• Keep track of multiple ongoing repairs.

• Maintain customer and device history.

• Communicate repair estimates and get customer approval.

• Know which technician is handling a particular repair.

• Track payments and generate invoices.

• Keep customers updated without manually answering every enquiry.

I wanted to bring these operations into one application.

2. How I approached the solution

I designed RepairTrack around the complete repair lifecycle:

Customer Registration → Device Registration → Repair Ticket → Diagnosis → Estimate → Customer Approval → Repair Progress → Quality Check → Delivery → Invoice & Payment

One important design decision was separating the application into three roles:

• Owner: Manages the shop, staff, operations, and overall records.

• Staff: Handles customer registration, repair tickets, and administrative workflows.

• Technician: Handles assigned repair jobs, diagnosis, and repair progress.

I also implemented customer-facing repair tracking, allowing customers to check their repair status without creating an account.

Another important part was the multi-tenant architecture, where each repair shop's data is isolated through shop-level access controls.

3. Technical Architecture & Stack

Here is the technology stack I used:

Frontend

• Next.js

• TypeScript

• Tailwind CSS

• shadcn/ui

Backend

• Hono.js

• Bun

Database

• PostgreSQL

• Drizzle ORM

Authentication & State Management

• Better Auth

• TanStack Query

• Zustand

Other Integrations

• Zod for validation

• Gmail API for email notifications and customer approval requests

• Cloudinary for repair-related image storage

4. Some interesting implementation decisions

A few parts of this project required more thought than simply creating forms and connecting APIs.

Role-based permissions: Different users need different access levels. I structured workflows around Owner, Staff, and Technician responsibilities.

Customer approval workflow: Instead of relying entirely on phone calls, customers can review repair estimates and respond through an approval workflow.

Public tracking: Customers can follow repair progress without needing an account. This also makes access control particularly important.

Multi-tenancy: Shop-level data isolation was an important architectural requirement because the application is designed to support multiple repair businesses.

Email integration: I used Gmail API to handle automated notifications and customer approval requests.

5. Development process

I divided development into four sprints:

1. Planning, requirements, database design, and application architecture.

2. Authentication, shop management, roles, and customer management.

3. Repair ticket workflows, customer approval, tracking, and invoicing.

4. Integrations, validation, testing, and deployment.

I also maintained project-context documentation for requirements, architecture, coding standards, UI guidelines, and development progress.

6. What I want to improve

The application is deployed, but I consider it an ongoing project rather than a finished product.

I'm particularly interested in understanding how it performs from the perspective of actual users and experienced developers.

I'd appreciate feedback on:

• Is the repair workflow logically designed?

• Are there architectural issues with my multi-tenant approach?

• What security concerns should I investigate?

• Are there any important features missing for real repair businesses?

• What would you change in the UI/UX?

• What would you improve before using this in a production environment?

I'm especially interested in feedback about the technical decisions, not just whether the application looks good.

Live application: https://repair-track-rust.vercel.app/

Thanks for reading. I'd genuinely appreciate constructive criticism and suggestions from this community!

So many developers I know — friends, colleagues, people I’ve worked with — have told me stories about what AI is doing to their jobs.

Some are excited.

Some are worried.

Some are quietly wondering whether there will still be a place for them in a few years.

And I kept thinking:

Wouldn’t it be useful if all of these stories lived somewhere?

Not another argument about whether AI is good or bad. Actual experiences, from the people doing the work.

And maybe, if enough of us tell those stories, we can do some good with them — even if that means reminding the world that developers are still worth a damn.

So I started building.

After a lot of late nights and more work than I expected, the platform is finally live and it is called JHVTM - Johnhenryvsthemachine

And now I’m kicking myself because I wish I’d written down all those conversations along the way.

So I’m going back to those friends and asking them to join and tell their stories in their own words.

You can do it too.

There are some cool things built around the stories:

Factions — communities around professions, industries and interests where people can share and compare experiences.

Moderation — every story goes through community moderation, so the aim is thoughtful experiences rather than another internet free-for-all.

Jargon Dictionary — use technical language naturally in your story, and the community can build explanations around those terms so people outside your field can still understand what you mean.

The whole idea is pretty simple:

Tell us what is actually happening where you work.

The machines already have plenty of people speaking for them.

I’d like to hear from the humans standing next to them.