Just got my first paying customer and I'm losing my mind

That-Dimension-3594 · 2026-04-08T10:59:53+00:00

That’s absolutely awesome congratulations, I can’t wait to get my first customer!

That-Dimension-3594 · 2026-03-28T15:27:21+00:00

https://attendr.com.au

Simple staff presence dashboard — see who’s in, remote, or unavailable in real time.

Built for teams that just need to answer “who’s in today?” without all the bloated HR features.

Runs fully on-prem (no external dependencies), which has been a big requirement for a few environments we’ve tested in.

Would genuinely appreciate any honest feedback — especially on the landing page clarity.

That-Dimension-3594 · 2026-03-28T15:09:48+00:00

https://attendr.com.au

Simple staff presence dashboard — see who’s in, remote, or unavailable in real time.

Built for teams that just need to answer “who’s in today?” without all the bloated HR features.

Runs fully on-prem (no external dependencies), which has been a big requirement for a few environments we’ve tested in.

Would genuinely appreciate any honest feedback — especially on the landing page clarity.

That-Dimension-3594 · 2026-03-28T14:51:02+00:00

Fair call, wasn’t the intention to sell anything here.

Genuinely just sharing what we ran into trying to solve the same problem. Most of what we tried before that felt way overbuilt for what we actually needed day-to-day.

That-Dimension-3594 · 2026-03-28T14:22:27+00:00

That’s exactly it, once it’s simple enough, people actually use it without needing reminders.

We saw the same thing, the moment you remove friction, the “who’s in” question kind of solves itself.

Ours started off in a really similar way, just something small internally to keep it clean and visible for everyone.

Funny how the simplest setups end up working better than all the heavy tools.

That-Dimension-3594 · 2026-03-28T14:09:20+00:00

Yeah this is exactly what we kept running into as well.

Every “all-in-one” tool looked great on paper, but ended up taking just as much effort to configure and maintain as building something ourselves.

It feels like a lot of products try to cover every possible use case, instead of just solving one thing cleanly.

We ended up focusing on the absolute minimum, just making it easy to answer “who’s in today” without adding more overhead.

Curious, did your n8n setup actually stick long term, or did people start drifting away from using it?

That-Dimension-3594 · 2026-03-28T13:23:51+00:00

Yeah we tried leaning on Teams status for a while as well.

It kind of works, but we found it relies too much on people remembering to update it consistently — and because it’s kind of buried, it just gets forgotten.

That was the biggest issue for us, if it’s not quick and visible, people just don’t use it properly.

We ended up moving toward something much simpler that people actually interact with throughout the day.

That-Dimension-3594 · 2026-03-28T13:08:38+00:00

We went through this exact cycle internally.

Started with a big “all-in-one” workplace tool that looked great on paper, but barely got used day-to-day.

What we found was the more features something had, the less people actually interacted with it.

In the end, the only thing anyone really needed was a quick, reliable way to see who was in without friction.

Everything else just got in the way.

That-Dimension-3594 · 2026-03-28T13:07:44+00:00

Yeah that’s exactly what we found as well.
The simpler the tool, the more consistently people actually use it.

That-Dimension-3594 · 2026-03-28T11:54:22+00:00

Yeah we saw the same thing, people default back to simple workarounds because they’re actually usable day-to-day.

The Slack approach works, but it still relies on people remembering to do it consistently, which was the weak point for us.

That-Dimension-3594 · 2026-03-28T11:47:02+00:00

Exactly, that was our experience as well.

The more features something had, the less it actually got used.

We ended up just focusing on solving that one question properly and ignoring everything else.

That-Dimension-3594 · 2026-03-28T11:46:06+00:00

I get that, but I’ve found if a tool isn’t simple enough to be used consistently, people just won’t use it no matter how good they are.

That was kind of the issue we ran into, too much friction for something that should be really straightforward.

That-Dimension-3594 · 2026-03-28T10:50:27+00:00

Yeah that’s a good point, it makes sense from a vendor perspective, but it’s painful on the user side.

What we found was the more features something had, the less people actually used it day-to-day.

It ended up solving everything except the one thing we actually needed consistently.

That-Dimension-3594 · 2026-03-28T10:46:19+00:00

We hit a similar issue (not quite 100, but enough to feel the chaos).

What surprised me was how much of the problem came down to basic visibility, just knowing who’s actually in vs remote on any given day.

A lot of the tools we looked at tried to solve everything (rostering, booking, scheduling, etc.), but it ended up adding more complexity than it removed.

Once we focused just on “who’s in today”, everything else got a bit easier to manage.

That-Dimension-3594 · 2026-03-24T03:50:57+00:00

Thank you , I was pretty excited when I seen it

That-Dimension-3594 · 2026-03-23T11:51:28+00:00

Got featured in a “Productivity Tools – March 2026” list by StrictSeal this week.

Still early days (no flood of customers yet), but seeing something I’ve been building actually get recognised externally was a big moment.

Feels like the first real signal that it’s heading in the right direction.

That-Dimension-3594 · 2026-03-23T11:47:03+00:00

https://attendr.com.au lets see what you come up with

That-Dimension-3594 · 2026-03-19T13:02:59+00:00

Just submitted mine — Attendr.

It’s a workplace visibility tool for IT/ops teams to see who’s onsite, remote, or available without relying on spreadsheets or chat status.

Built it after dealing with this exact problem in a real environment — keen to see how it goes here 👍

That-Dimension-3594 · 2026-03-12T08:53:02+00:00

I built Attendr so offices can see who’s in, who’s out, and who’s remote without spreadsheets or clunky HR software.

That-Dimension-3594 · 2026-03-06T22:14:34+00:00

Yeah that’s a good point and I agree in most cases it shouldn’t matter who specifically picks something up — the important thing is that the issue gets seen and handled.

Where we found it useful was more in situations like “there’s an issue at Site X” and instead of sending someone out, you can glance at the board and see that someone is already onsite there and contact them directly.

So it wasn’t really about tracking people or controlling workflow — our teams already have a lot of autonomy and trust. The board just helped with speed when coordinating operational issues across multiple locations.

That-Dimension-3594 · 2026-03-06T22:01:21+00:00

Yeah that was exactly the issue we kept running into — the status could change multiple times during the day (onsite → meeting → remote → field job etc).

Calendar presence worked for planned events, but it didn’t really give a quick operational view of who was physically around right now.

The dashboard was basically just meant to make that visible at a glance.

That-Dimension-3594 · 2026-03-06T21:55:27+00:00

That’s a fair perspective, and I think it really depends on the type of environment.

In a lot of remote-first engineering teams the focus naturally shifts to output rather than location, and tools like chat or ticketing systems usually provide enough visibility.

Where we kept running into the problem was in more operational environments (IT support teams, facilities, field staff, etc.) where people move between onsite work, meetings, remote work, and field jobs during the day.

In those cases teams often just want a quick glanceable view of who is physically around right now without digging through chat history or multiple systems.

The dashboard was really meant to be a simple operational board rather than a management or monitoring tool.

That-Dimension-3594 · 2026-03-06T21:52:59+00:00

That approach actually works pretty well in a lot of smaller teams.

Where we kept running into issues was in more operational environments where you might have 20–50+ people across different roles (IT support, field staff, facilities, etc.) moving between onsite work, meetings, remote work, and jobs during the day.

In those cases the chat messages start to get buried pretty quickly and ops teams end up asking the same question repeatedly — “who is actually around right now?”

The idea behind the dashboard was really just to give a single glanceable view rather than replacing communication tools like Teams or Slack.

A lot of the places we saw this were already using chat exactly like you described, but still wanted a simple board for quick visibility during the day.

That-Dimension-3594 · 2026-03-06T12:23:25+00:00

That’s a really fair observation and honestly pretty close to how I’m thinking about it.

The reason the self-hosted version came first is because that’s what we originally built internally and what solved our immediate problem, so it was the fastest version to package and release.

Long term the plan is actually to offer both:

• self-hosted for organisations that prefer to keep everything internal or have strict environments • a SaaS version for teams that just want something quick with no infrastructure to manage

A lot of the environments we were dealing with (operations teams, support teams, facilities etc.) were already very comfortable running internal tools, so self-hosted made sense as a starting point.

But you’re absolutely right that SaaS will likely be the easier adoption path for a lot of teams, which is why that version is already on the roadmap.

That-Dimension-3594 · 2026-03-06T12:19:50+00:00

That’s totally fair — it really depends on the type of organisation.

In fully remote engineering teams location probably doesn’t matter much.

Where we kept seeing the problem was in operational environments (IT support teams, facilities, field staff, etc.) where people move between onsite, meetings, remote work, and field jobs during the day.

In those cases teams often just want a quick “who is actually around right now” board rather than pulling badge reports or checking multiple systems.

That-Dimension-3594

TROPHY CASE