How to pick fiber network management software — an 8-point checklist.

We've watched operators evaluate fiber GIS software for the last several years. The good evaluations look a certain way; the bad ones look another way. Here's the 8-point checklist that consistently separates them.

1. Does the vendor publish pricing?

If the answer is no, that tells you several things — none of them good. Hidden pricing means custom quotes per customer (which usually means "we charge what we think you'll pay"), longer sales cycles (which means slower implementations), and procurement friction.

More importantly: hidden pricing is a category convention that everybody has accepted. Vendors who publish prices are signaling something specific about how they want to do business.

2. Is the data model telecom-native or generic GIS?

Generic GIS lets you draw any feature class with any attributes. That sounds flexible until you realize every operator has to build their own data model, badly. Telecom-native means strands, splices, splitters, OLTs, ONTs, NIDs, NAPs are first-class objects out of the box.

Test this in evaluation: ask the vendor to show you how a splice closure with 12 trays and 144 strands is represented. If the answer involves "custom feature class" or "data model configuration," deduct a point.

3. How long does deployment actually take?

Deployment timeline is one of the highest-variance numbers in this category. Self-serve SaaS: 1 day. Modern fiber GIS with assisted onboarding: 30 days. Esri Utility Network: 6–18 months.

Ask vendors for specific customer-time-to-go-live numbers. "Our fastest customer went live in 4 weeks" is meaningful; "our typical deployment is 3–6 months" is also meaningful.

4. Is mobile a single app or a stack?

Esri's field workflow needs Field Maps + Survey123 + QuickCapture + Workforce — four apps for one job. Modern alternatives use one app. Crews adopt single apps. They don't adopt 4-app stacks.

Test: Have the vendor demo a field workflow on an iPhone. If they have to alt-tab between apps, deduct a point.

5. Does it integrate with what you already run?

REST API is table stakes. Webhooks are table stakes. Two-way conversion to/from ArcGIS, AutoCAD, KMZ, Shapefile is table stakes. SSO (Okta, Azure AD, Google) for enterprise customers is table stakes.

If the vendor is missing any of these, you're either building integrations yourself or paying them to build them. Both are expensive.

6. What does the audit log actually contain?

Every state-changing action should write an immutable record: who, when, what changed, before/after. The log should be queryable via API and exportable. SOC 2 Type II controls should govern access.

Most operators don't need to query the log every day. But the day they need it, they really need it.

7. How does the vendor handle BEAD compliance?

If you're a BEAD recipient (or expect to be), this matters disproportionately. State-specific reporting templates. Eligibility-fabric overlays. Challenge process management. Auto-generated submission packages.

If the answer is "we have an export to CSV — you can build the report yourself," deduct a point. That's not BEAD support; that's CSV export.

8. What happens when you outgrow the tier?

Pricing should scale predictably. Surprise overages, mandatory tier upgrades, or sudden 3× quotes are the hallmarks of vendors who don't want you to know what you're paying for.

Ask: what's the path from Starter to Pro to Enterprise? Is it a usage-based add-on or a forced re-negotiation? You want the first.

Vendor scorecard: IQGeo vs VETRO vs 3-GIS vs MapItRight on the 8 points

Every vendor will tell you they meet all 8 criteria. Here's our honest assessment based on public information and customer feedback as of May 2026. We're MapItRight — so read this skeptically and verify on demos with each vendor.

• ·1. Published pricing: MapItRight ✓ published. VETRO ✗ quote only. IQGeo ✗ /pricing returns 404. 3-GIS ✗ quote only.
• ·2. Telecom-native data model: MapItRight ✓ built in. IQGeo ✓ (OSPInsight heritage). VETRO ✓ ISP-native. 3-GIS ◑ Esri-dependent, requires configuration.
• ·3. Deployment speed: MapItRight 30 days typical. VETRO 3–6 months. IQGeo 3–9 months. 3-GIS 3–9 months (includes Esri setup).
• ·4. Single mobile app: MapItRight ✓. VETRO ◑ multi-screen. IQGeo ✓ (multi-product stack though). 3-GIS ✗ Esri Field Maps stack.
• ·5. Integration ecosystem: All four vendors offer REST APIs. IQGeo has the most mature OSS/BSS connector library. MapItRight and VETRO are comparable on standard integrations.
• ·6. Audit log quality: MapItRight ✓ SOC 2 Type II immutable. IQGeo ✓. VETRO ◑. 3-GIS ◑ depends on Esri config.
• ·7. BEAD compliance built-in: MapItRight ✓. VETRO ◑ partial. IQGeo ◑ custom build. 3-GIS ✗ manual.
• ·8. Scaling path: All four vendors have enterprise tiers. Pricing transparency at scale varies — only MapItRight publishes all tiers.

12 questions to ask during any fiber GIS demo

1. Can you show me strand-level connectivity from an OLT port to a specific subscriber ONT in under 30 seconds?
2. What's the actual deployment timeline for a customer at my scale — not the sales deck estimate?
3. Can you show me BEAD eligibility overlaid against a real network in the design canvas?
4. What does migration from my current platform look like — specifically, who does the work and what's the timeline?
5. Can I see your pricing page? (If they say 'let me get you a quote', note that as a yellow flag.)
6. What's the mobile app experience — single app or multiple apps?
7. Show me the audit log — specifically, can it be edited or deleted retroactively?
8. What happens to my data if I cancel? What export formats are available?
9. How many customers at my subscriber count are currently live on the platform?
10. What does the implementation team look like — is it the vendor or a partner SI?
11. What's the BEAD challenge process workflow — walk me through a challenge end to end?
12. What's on your 12-month product roadmap, and how much is publicly committed vs internal-only?

Putting it together

Score each vendor 0–1 on each of the 8 dimensions. Anyone scoring 6+ is worth piloting. Anyone scoring 3 or below is probably not in your category, regardless of brand recognition.

Want our 30-point detailed evaluation matrix? It's available — book a demo and we'll send it. Or skip the demo and just read /pricing — the most important question is on the page.