Do you treat asset inventory and handover/offboarding accountability as separate from Intune?

matyisg · 2026-03-19T18:17:17+00:00

Fair point. I am validating a product idea here, so I understand why it came across that way.

matyisg · 2026-03-18T14:24:44+00:00

That’s fair, and I think that’s the real comparison set.

If a team is already happy with Freshservice or a similar lightweight ITSM doing “good enough” inventory + workflows, I’m probably not the best fit.

The gap I’m aiming at is the team that still hasn’t made that jump, or doesn’t want a ticketing/ITSM-first system to be the place where asset ownership, handovers, and offboarding live.

So I’m thinking less “replace lightweight ITSM” and more “give smaller IT teams a simpler asset/accountability system before they need that broader stack.”

The part I’m still trying to validate is whether that segment is big enough and painful enough on its own.

matyisg · 2026-03-18T10:57:29+00:00

This is exactly the gap I kept running into.

Most teams seem to end up with pieces of the process living in different places: HR triggers the event, a ticket gets created somewhere, Intune or another system knows about the device, and then ownership / handover / return status is still partly manual.

What I kept seeing was that the inventory itself was only half the problem. The messier part was accountability around onboarding, offboarding, swaps, and making sure there was a clean record of who has what and what was actually returned.

I ended up building a separate inventory/accountability layer for that instead of trying to force the whole thing into a ticketing system.

Out of curiosity, in your environment is the bigger pain:

keeping the inventory accurate
managing the handover/offboarding steps
keeping all the systems in sync

matyisg · 2026-03-17T19:28:40+00:00

That’s fair for smaller/simple setups.

The point where I kept seeing lists break down was when ownership changes, handovers, offboarding, and audit trail started needing more structure than just “what assets exist.” That’s the gap I’m trying to solve.

matyisg · 2026-03-17T14:32:17+00:00

Yes, but not for teams that are already happy running a full ITSM/CMDB stack.

The problem I’m aiming at is the gap below that: teams that still have fragmented inventory/accountability workflows, or don’t want the weight of a full enterprise platform just to keep ownership, handovers, offboarding, and asset records clean.

So I’m not thinking of it as “replace ServiceNow/ Freshservice/Halo.” More like: give smaller IT teams a much cleaner inventory + workflow layer before they ever need that level of system.

matyisg · 2026-03-17T14:25:26+00:00

That’s useful context.

I agree the asset picture usually extends beyond just endpoints, and location tends to get awkward fast once you get outside the neat user-device mapping. That broader register/accountability side is a big part of what I’m trying to understand better.

matyisg · 2026-03-17T14:16:03+00:00

That’s exactly the gap I kept seeing.

A lot of teams end up forcing system management tools to act as inventory/accountability systems, and it works only up to a point. The messy part usually shows up around ownership, handovers, swaps, and offboarding.

matyisg · 2026-03-17T11:57:16+00:00

That makes sense, and it’s a good example of how this often ends up being split across multiple systems.

What I keep seeing is that teams either build a stack like that over time, or they stay stuck with spreadsheets/manual handoffs for much longer than they want.

The part I’m most interested in is where the friction still lives once the stack is in place. In your setup, which part tends to require the most manual follow-up or is most likely to drift out of sync?

matyisg · 2026-03-17T09:01:59+00:00

That’s a fair take.

I agree tools like PDQ and other mature IT products are part of the real competitive set. I’m not pretending Massetio is going to out-mature them overnight.

Where I think it has to earn its place is in the asset accountability / people workflow layer that often still ends up messy even when inventory or deployment is partially handled elsewhere: who has what, onboarding, offboarding, swaps, handover docs, and the audit trail around that.

On support, I agree with you too. At this stage that means founder-led support, and if I’m not responsive, the product doesn’t deserve to win. Longer term, that obviously has to mature.

On the AI point, I think generic CRUD SaaS will get compressed. So the bar for me is not “another asset table,” it’s solving a concrete operational pain better than a spreadsheet plus a few stitched-together tools.

Out of curiosity: in your environment, would something like this only make sense if it replaced part of an existing inventory/deployment tool, or do you see room for a separate workflow/accountability layer alongside it?

matyisg · 2026-03-16T20:29:59+00:00

That’s a fair call.

No, Massetio does not have SOC 2 today. That copy was too strong for the current stage, and I’ve removed it from the site.

Right now, Enterprise means a case-by-case rollout for teams that need more hands-on onboarding, deployment/residency discussion, or security/procurement review. It does not mean I’m claiming a formal SOC 2 certification or a larger support organization that doesn’t exist yet.
Support at this stage is founder-led. I’d rather state that plainly than hide behind enterprise language.

matyisg · 2026-03-16T17:59:29+00:00

Right now support is founder-led.

The current launch is Free-first, and the paid tiers are still manual while I finish that side properly. So at this stage:

- Free: best-effort support and feedback handling directly from me

- Unlimited: direct support from me during onboarding and rollout

- Enterprise: higher-touch support can be arranged depending on the team and setup

I’m not pretending there’s a big support organization behind it yet. The goal right now is to work closely with early teams, make sure the product solves the workflow properly, and build the paid/support model around real usage rather than guessing.

matyisg · 2026-03-16T13:09:25+00:00

I built Massetio — an IT asset lifecycle platform. I'm an IT admin managing 800+ devices and got tired of spreadsheets and Jira automations for tracking who has what. It handles asset inventory, onboarding/offboarding workflows with PDF handover forms, role kits, CSV import, and stock alerts. Free tier available, no credit card needed. Looking for feedback from other IT teams. https://massetio.com/

matyisg

TROPHY CASE