Explore our most common inquiries about DecisionPoint Technologies, our services, and how we support your enterprise mission.
The readiness conversation itself is typically a single working session. The phased roadmap that follows depends on how many sites, systems, and asset types are involved, but it’s scoped in weeks, not months, because the point is to start with the next right step, not a full transformation plan.
It depends on how much the workflow genuinely differentiates you and whether you want the ongoing responsibility of owning, maintaining, and evolving custom code. AI has made writing code cheaper, but it hasn’t reduced that long-term commitment. We walk through that tradeoff with you rather than defaulting to either answer.
Look for a partner who asks about your operation before talking about their platform, who can explain how your existing systems (MDM, carrier, procurement, directory) should connect rather than be replaced, and who’s willing to tell you when buying beats building.
Fewer “where is it” questions, faster issue resolution without escalation, and, eventually, proactive workflows where the system flags what needs attention before someone has to go looking. Those signals typically show up well before any formal ROI model is built.
We start with readiness, not features. Most AI ambitions stall because the organization skipped straight to automation without digitizing and optimizing first. We help you find where you actually are on that curve before recommending any technology.
You need enough visibility to answer the specific question you’re trying to solve with AI. AI can’t compensate for missing or inconsistent data, so the practical first step is treating AI readiness as a data initiative: define the real problem, then check whether the data to solve it actually exists.
It means using AI, automation, and orchestration to turn asset data into real-time decisions, alerts, and actions, but only once the underlying visibility and data quality can support it. AI doesn’t replace asset visibility; it depends on it.
We’re here to scale with you. For the Fixed Assets, Rotational Assets, and Consumable Inventory bundles, extra seats incur an extra license charge. For IT Assets customers, seats are unlimited so new users are easy to add.
Support is included in the StayLive platform pricing and customers can choose whether they need 8/5 or 24/7 support.
Yes, there is a one-time GoLive cost to get you set up with your IntelliTrack platform.
Standard training is included in our solution pricing. Standard training includes access to all IntelliTrack training assets and up to two hours of instructor-led web based product training. Additional training can be included for an extra cost if necessary.
Sure, let’s check out an example!
Let’s say your company is growing and ready to invest in your digital transformation.
Let’s also say you’re a Retail Operations Manager and you need to know specifically how many IT assets (mobile scanners and label printers) you have at the store and how many are out for repair.
Based on this simple criteria, we might recommend starting with two bundles—IT Assets and Rotational Assets.
Platform pricing would be based on the number of mobile scanners/printers you would like to track with additional licensing costs for the Rotational Asset functionality.
As a next step, we might recommend pairing this solution with Consumable Inventory to track other critical inventory items that keep the IT assets running like printer cartridges and batteries.
Down the road, we might also recommend adding Fixed Assets so the retailer can begin to track laptops and other assets all in one place.
We won’t just hand over devices and cross our fingers. Our process starts with setting expectations and setting change management plan. We offer our clients plenty of training options to help, but the real key to user adoption is to involve end users early in the process. The more you build champions along the way, the more likely you’ll have success. While people often fear the change, once they understand the new technology, they love it.
Sorry, but we firmly believe you will not save money and on top of it, you will put your organization at risk for security breaches.
Consider the cost to your organization if you were to get hacked (a real possibility with any old technology): the downtime you’d experience (and potential loss of business) could be catastrophic to your reputation and bottom line. And, organizations that try to keep old technology on board eventually have to fund a much larger, more complex move to new technology.
The readiness conversation itself is typically a single working session. The phased roadmap that follows depends on how many sites, systems, and asset types are involved, but it’s scoped in weeks, not months, because the point is to start with the next right step, not a full transformation plan.
It depends on how much the workflow genuinely differentiates you and whether you want the ongoing responsibility of owning, maintaining, and evolving custom code. AI has made writing code cheaper, but it hasn’t reduced that long-term commitment. We walk through that tradeoff with you rather than defaulting to either answer.
Look for a partner who asks about your operation before talking about their platform, who can explain how your existing systems (MDM, carrier, procurement, directory) should connect rather than be replaced, and who’s willing to tell you when buying beats building.
Fewer “where is it” questions, faster issue resolution without escalation, and, eventually, proactive workflows where the system flags what needs attention before someone has to go looking. Those signals typically show up well before any formal ROI model is built.
The readiness conversation itself is typically a single working session. The phased roadmap that follows depends on how many sites, systems, and asset types are involved, but it’s scoped in weeks, not months, because the point is to start with the next right step, not a full transformation plan.
It depends on how much the workflow genuinely differentiates you and whether you want the ongoing responsibility of owning, maintaining, and evolving custom code. AI has made writing code cheaper, but it hasn’t reduced that long-term commitment. We walk through that tradeoff with you rather than defaulting to either answer.
The readiness conversation itself is typically a single working session. The phased roadmap that follows depends on how many sites, systems, and asset types are involved, but it’s scoped in weeks, not months, because the point is to start with the next right step, not a full transformation plan.
It depends on how much the workflow genuinely differentiates you and whether you want the ongoing responsibility of owning, maintaining, and evolving custom code. AI has made writing code cheaper, but it hasn’t reduced that long-term commitment. We walk through that tradeoff with you rather than defaulting to either answer.
Look for a partner who asks about your operation before talking about their platform, who can explain how your existing systems (MDM, carrier, procurement, directory) should connect rather than be replaced, and who’s willing to tell you when buying beats building.
Fewer “where is it” questions, faster issue resolution without escalation, and, eventually, proactive workflows where the system flags what needs attention before someone has to go looking. Those signals typically show up well before any formal ROI model is built.
We start with readiness, not features. Most AI ambitions stall because the organization skipped straight to automation without digitizing and optimizing first. We help you find where you actually are on that curve before recommending any technology.