Skip to main content

​
When should I contact Placematic?

Short answer: When the question is commercial — entitlements, contracts, redistribution, pricing tiers. Not when the question is architectural, because those answers are in these docs.

​
Contact us before

You scope a sprint around an API. Ten minutes confirming entitlement beats a quarter discovering a 403. You build a business case on asset-based pricing. Availability depends on contract tier. Confirm before it’s load-bearing in front of your CFO. You embed HERE into a product you sell. The redistribution question carries different licensing terms than internal use. Resolve it before you ship, not during a customer’s security review. You design a permanent geocode cache. Retention of geocoded coordinates is a contract term. Get it in writing. You plan a mobile release. Web tile access and mobile SDK access are separate entitlements. Discovering this at app store submission is expensive. You want a cost evaluation. Bring per-endpoint call counts from your logs. Not estimates. You already license HERE directly and want to know whether a partner contract improves your terms. Bring the contract.

​
Don’t contact us for

Most of what determines whether your location platform succeeds does not require a vendor conversation.
“How do I reduce my bill?” Cache geocoding. Batch what tolerates latency. Debounce autocomplete. Deduplicate. Stop reverse-geocoding GPS packets. Replace routing loops with matrix calls. Do that first, re-measure, and then the conversation is worth having. See Cost Optimization Patterns. “Should I use Routing or Matrix?” If you’re writing a loop, you already know. See Routing vs Matrix. “Is HERE better than Google?” For consumer place discovery, no. Categorically. See HERE vs Google Maps. “Should I self-host OSM instead?” Maybe. Test whether the truck restriction tags exist in your operating region first. It takes an afternoon and it frequently ends the discussion. See HERE vs OpenStreetMap. “Is my architecture right?” Read Architecture. If it still isn’t clear, then ask.

​
And genuinely don’t migrate if

Your spend is under roughly $1,000/month after optimization. The payback period on migration engineering is measured in years. Do something else. Your product’s core value is consumer place discovery. Keep Google. You have no engineering capacity this quarter. A half-finished migration is worse than either endpoint. The only argument is “cheaper.” Cheaper on a feature that regresses is not cheaper.
We sell HERE. If we thought a migration would fail, telling you now costs us one deal and buys credibility for the ones worth doing.

​
What to bring

  • Per-endpoint call counts, from logs
  • What you’re building, specifically — vehicle class, geography, volume
  • Your current contract, if you have one
  • Your worst month, not your average

What support does Placematic provide?

Including what we don’t.

Reducing Google Maps Costs

Do this before you call anyone.

How do I test before production?

Entitlement checks you can run yourself, today.

Do I buy from HERE or Placematic?

Including when to go direct.
Need production HERE API keys or implementation support? Placematic is an official HERE Technologies reseller and implementation partner. Talk to us, or run the Cost Reduction Audit first.