Opening a new company, subsidiary or operation? Kasnol takes on technology end to end — from the first design to day-to-day support. You run the business; we deliver IT that works, secure and governed.
Every new operation needs technology on day one — and almost none has, at that point, an IT function to take care of it.
A company being built from scratch, with no IT function and no time to build one before it starts selling.
An international group entering Brazil or Latin America that needs local IT aligned with headquarters' standards.
An expansion — office, plant or distribution center — that must be born integrated with what already exists.
An operation separating from a group that needs its own systems before the cut-over date.
Each phase has its own scope, deliverables and price. At the end of each, you decide — with a recommendation and numbers on the table — whether and how to proceed.
We understand the business before we talk technology. We define the operating model, requirements and architecture — and select the platforms, ERP included, based on evidence, not brand.
Platforms selected and implementation plan approved.
We run the implementation from the client side: one integrated plan, a single design authority and every vendor under control — scope, schedule, budget, risk and acceptance.
Go-live approved and operation stabilized.
After go-live, we remain your IT function: leadership, support, security and vendors — with KPIs, management rituals and continuous improvement.
An in-house team, if and when growth justifies it — and we help build it.
Indicative timelines for operations with no legacy systems to migrate. The critical path is rarely technical: it usually runs through standards decisions, company incorporation, banking and tax registration.
What opening a new operation would look like in practice with Kasnol leading technology — and what stays with you at each stage.
Hypothetical situation, built from our methodology. It does not represent a client or a real project.
A renewable-energy group creates a new company to operate in Brazil: head office in Campinas, field teams in three states and about 40 people in the first year. There are no systems and no IT function — and the start date for operations is already set.
Kickoff with leadership, decision map and program calendar.
Names a sponsor and shares the business plan.
Maps processes, defines requirements and architecture, runs scripted demonstrations and compares the platforms' total cost.
Joins short workshops and decides at the gate, with a recommendation and numbers on the table.
Sources and coordinates vendors; implements ERP, collaboration, network, devices and security; runs testing and training.
Follows a bi-weekly executive status and approves go-live.
Every employee receives a ready-to-use device, with secure access to what they need — and support from the first hour.
Opens the doors. The technology is already there.
Runs as the company's IT function: support, security, vendors, KPIs and evolution.
Receives monthly KPIs and sets priorities at the IT committee.
Each area can be engaged on its own. The value comes from one party seeing the whole picture — and being accountable for it.
IT model, standards, roles and decision forums.
Requirements, RFP, demonstrations and business case.
Data ownership, interfaces, controls and monitoring.
Email, collaboration, documents and single identity.
Cloud, network, connectivity, telephony and devices.
Identity, MFA, endpoint protection and incident response.
LGPD, GDPR, retention and cross-border data transfer.
Sourcing, technical negotiation and service levels.
Backup, tested recovery and contingency plans.
Service desk, service management and continuous improvement.
We choose platforms and vendors based on evidence and are accountable for the whole — not for a product or a brand.
Identity, multi-factor authentication, encryption, tested backup and LGPD/GDPR are part of the design, not an afterthought.
The same team that conceives the operation stays with it after go-live, with no knowledge lost along the way.
In 30 minutes, we'll understand the context and give you an honest read on the path — and on what needs to be decided first.