Choosing an Internal Tool Platform: The Questions Vendors Won't Answer for You

Data export, API limits, permissions, pricing traps and audit logs: a buyer's checklist for internal tool platforms that goes beyond the feature grid.

Every platform demo goes the same way. A sample project-tracking app appears in four minutes, a form populates a table, an automation sends a message to your chat tool, and everyone nods. Nobody asks what happens when you have 80,000 records, or when you want to leave.

The feature grid tells you what a platform can do on a good day. This checklist is about the other days.

Can you get your data out, completely?

Start here, because it’s the question that matters most and gets the vaguest answers.

“Yes, you can export to CSV” is not a complete answer. A CSV (a plain text file of rows and columns) usually holds one table at a time. Ask what happens to everything else:

Relationships. If a client record links to five projects, does the export keep those links, or do you get a column of display names you’ll have to match back up by hand?
Attachments. Are files included, or just links that stop working when your account closes?
History and comments. Does the change history come with you, or only the current values?
Automations and logic. Can you export the rules themselves, even as a readable document, or do they exist only inside the platform?

Then ask for a demonstration. Have them export a sample workspace with linked tables and attachments, and look at the result yourself. “Backups, Exports and Exit Plans: Protecting Your Data in Someone Else’s Cloud” covers how to make this a routine, not a one-off.

What are the limits, and what happens when you hit them?

Every platform has ceilings. They’re usually on a pricing page, in small print, or discovered at 4pm on a Friday.

Ask about:

Record limits per table and per workspace. Say you log 300 support requests a week. That’s over 15,000 a year. Does that fit on the plan you’re considering?
Automation runs. Many platforms cap how many times automations can fire per month. A single automation that runs on every record update can burn through a monthly allowance in days.
API limits. An API is the way other software talks to the platform. Limits on API calls determine whether your integration with the CRM or accounting system can keep up, or will quietly fall behind during busy periods.
File storage. Attachments add up fast, especially photos and scanned documents.

The important follow-up is: what happens at the limit? Does it stop working, slow down, warn you, or silently skip things? Silent skipping is the worst answer, and you want to know about it before it happens.

How granular are the permissions really?

Spreadsheets are all-or-nothing. That’s often why you’re leaving. Make sure the new platform is actually better.

Bring a real scenario. For example: “Regional managers should see and edit only records for their region. Finance should see every record but only edit the billing fields. Contractors should see only jobs assigned to them, and never see the pricing.”

Then ask the vendor to show you that configuration, not describe it. Common gaps include permissions that work at the table level but not the record level, field-level restrictions that are only available on the top pricing tier, and “hidden” fields that are still visible through an export or the API.

“Permissions That Make Sense: Who Should See and Edit What” goes deeper on designing roles once you’ve chosen.

Where’s the pricing trap?

Per-seat pricing is the usual one. It looks reasonable for the core team, then grows every time someone else needs access.

Work through these:

Question	Why it matters
Is there a cheaper read-only or viewer seat?	Many people only need to look things up
Do external users (contractors, clients) count as seats?	Can multiply your bill
Which features are locked to higher tiers?	Single sign-on, audit logs and fine-grained permissions often are
What’s the price increase history and contract cap?	Protects you at renewal
Is there a minimum seat count or annual commitment?	Affects small teams most

Single sign-on deserves a special mention. It lets staff log in with their existing company account, and it lets IT disable access in one place when someone leaves. It’s frequently reserved for an enterprise tier, which can double the price. Find out early.

Can you see who changed what?

When something goes wrong in a spreadsheet, you usually can’t tell who did it. An audit log fixes that: a record of who viewed, created, changed or deleted what, and when.

Ask:

Is there an audit log, and on which plan?
Does it cover data changes, permission changes, and changes to automations, or only some of these?
How long is it kept? Thirty days is not much use for an annual audit.
Can you export it, or only view it on screen?

If you handle anything regulated, such as financial approvals or personal data, this isn’t a nice-to-have.

What does support and reliability look like?

You’re about to run a business process on this platform. Ask the questions you’d ask of any critical supplier.

Is there a published uptime record and a status page?
What’s the support response time on your plan, and is it email-only?
Where is your data stored, geographically? Some industries and clients will ask.
What notice do you get before features change or are removed?

Also ask about their customers who look like you. A platform full of five-person startups may not be ready for your 200-person operations team, and vice versa.

Where to start this week

Write down one real permissions scenario and one real volume estimate from your documented process, and send both to each vendor on your shortlist.
Request a full export of a demo workspace with linked records and attachments, and open the result yourself.
Price out the plan you’d actually need in two years, including single sign-on, audit logs and every viewer seat.
Ask each vendor, in writing, what happens when you hit each usage limit.