Why we compare integration with replacing the readers
Replacing readers means buying devices, cables, licences, installation work and downtime at the gates. Integration leaves the readers in place: the AC system sends the punch event to InnerWeb with an HTTP POST webhook, and the further logic (training, permits, working time records) runs in the software. InnerWeb is a software vendor and integrates with the existing AC system as an independent complementary system alongside AC, RCP, HR and ERP.
For purchasing this changes the category of expenditure: instead of an investment in hardware there is an implementation service and a software subscription. Below we describe the cost items worth collecting from the AC vendor and from us before a decision is made.
Structure of the integration cost
The integration costs fall into one-off and recurring items. The prices in this section are indicative ranges from implementations in 2025 to 2026; an individual quote is required. We do not give amounts assigned to specific entities.
- Specification and analysis: preparing the requirements for the AC vendor on the basis of the integration document, usually several days of work.
- Sending configuration on the AC side: the event rule for the punch, the technical account, token handling and the retry queue. This is work of the AC vendor, quoted by them.
- Configuration on the InnerWeb side: reader place templates, training requirements, company mapping.
- End-to-end tests: punches on several readers, duplicates, unknown cards, a series of events.
- Maintenance: the software subscription and oversight of the integration.
What is not in this structure
There is no purchase of readers, cards or controllers, because InnerWeb does not supply them for this integration. There is also no replacement of the cabling infrastructure. If the AC vendor proposes replacing hardware as a condition of the integration, it is worth asking for a technical justification, because the webhook is a standard HTTP request.
One-off cost: replacement or integration (example)
Traffic volume and the cost of maintenance
The volume of card traffic affects the requirements, not the licence for readers: at a plant with many staffing agencies it may be more than 2,000 punches per working day. The webhook must withstand bursts of events and repetitions, which is why the specification includes a queue on the AC side and real-time sending.
InnerWeb provides an API and webhooks for integration with plant systems, so the same channel can later serve further scenarios, for example calling an external service after a no-movement alarm. This is an argument for purchasing: once built, the integration serves more than one purpose.
Example calculation: integration versus replacement
The comparison below is an example calculation on explicit assumptions, not an offer. The plant has 20 readers. Replacement requires buying devices and installation; integration requires configuration work. The unit values are adopted assumptions which each plant should replace with its own offers.
How to prepare the comparison for the purchasing committee
Collect three offers: from the AC vendor for the sending configuration, from us for the software side and from the reader vendor for the replacement variant. Compare the total cost over a horizon of several years, including maintenance. Ask the AC vendor whether punches can already be sent with an HTTP POST request today, because this shortens the implementation. Note that the integration alone, without mapping to entries, does not give RCP: at one installation the punches were visible only in the account change history, not in the entry register or in the working time records. The mapping is a separate item that must be included in the quote.
Replacing 20 readers versus integrating the existing AC system
| Parameter | Value |
|---|---|
| Number of readers | 20 pcs |
| Purchase and installation of one reader (assumption) | 3,000 PLN |
| Sending configuration on the AC side (assumption) | 12,000 PLN |
| Configuration and tests on the InnerWeb side (assumption) | 15,000 PLN |
Result: Replacement: 20 x 3,000 PLN = 60,000 PLN. Integration: 12,000 PLN + 15,000 PLN = 27,000 PLN. Difference in one-off costs: 33,000 PLN, excluding the subscription and excluding the gate downtime during replacement.
Note: Example calculation on explicit assumptions; indicative ranges from implementations in 2025 to 2026; individual quote required. The values do not relate to any specific plant.
Video
Frequently asked questions
Does InnerWeb sell readers for this integration?
No. InnerWeb is a software vendor and does not produce or replace AC readers. It integrates with the AC system the plant already has.
Does the integration give working time records straight away?
Not on its own. The webhook delivers the punches, and RCP requires mapping the punches to entries and exits. That element is quoted separately.
How should the amounts be read?
As an example with explicit assumptions. Actual prices are indicative ranges from implementations in 2025 to 2026; an individual quote is required.
Let's price the integration for your AC system
We will prepare a breakdown of cost items for purchasing based on the number of readers and the traffic volume. Book a call with the InnerWeb team.
Let's talk