A park district has a software problem long before anyone opens a laptop. It must turn people, positions, spending requests, and actual expenses into a budget that other people can understand. At the Chicago Park District, the trouble was familiar: manual processes and spreadsheets were doing work that needed a connected financial platform. That is the sort of assignment Krasan Consulting Services takes on. The interesting part is how much of the job happens between the applications.
- Krasan connects enterprise systems and redesigns the work around them.
- Its customers include public agencies, schools, and commercial organizations.
- Its published cases make training and patient listening part of delivery.
The spreadsheet reaches its limit
Krasan’s account of the parks project begins with a gap in the district’s ability to collect, report, and analyze financial and business information. The team developed a roadmap, reworked processes, and implemented Oracle Hyperion Public Sector Planning and Budgeting. It connected the planning environment with Oracle’s general ledger and built position-based reporting using business-intelligence and data-integration tools.
Translated from enterprise software into ordinary English: the budget could draw on actual financial activity, and staff could examine spending associated with positions. Deliverables included an electronic budget book, automated inputs for nonlabor requests, customized entry forms, training manuals, and system documentation. The manuals are a revealing detail. Someone has to operate the thing after the implementation team leaves.
The acquisition meets the accounting system
A second case offers a different kind of friction. Fellowes Brands wanted to move acquired businesses onto its Oracle EBS financial systems. One acquisition had manufacturing and business practices that differed substantially from the parent company’s. A technical migration could carry data across. Deciding how the combined business should work required conversation.
Krasan established requirements, configured software, developed the necessary additions, migrated data, tested functions, and trained staff. Its account gives unusual weight to balancing the acquired company’s successful practices against the way Fellowes and Oracle operated. Initial resistance and suspicion became a smoother transition through listening and practical choices, according to the case. Fellowes integrated the business on schedule and reduced redundant operating costs.
“Patient listening and presentation of realistic options were critical to the team’s success.”Krasan’s account of the Fellowes project
The useful lesson is modest enough to copy. Before declaring a process obsolete, ask what it accomplishes for the person who depends on it. The Fellowes account makes that negotiation central to the outcome. It suggests that adoption begins while requirements are being discussed, well before the training session appears on the calendar.
A consultant for the joins
Krasan occupies the space between management advice and hands-on systems integration. Its service menu stretches from executive consulting and process reengineering to user research, web and mobile development, project management, support, and staffing. An institution can buy help defining a problem, implementing a response, or supplying people to keep work moving. These are professional-service engagements with scope to agree.
The platform list is broad: Oracle and SAP for enterprise resource planning; Salesforce and Microsoft Dynamics for customer relationships; Drupal, WordPress, Adobe Experience Manager, Sitecore, Contentful, and Contentstack for content. Data analytics and AI sit alongside those established systems. The practical proposition is experience connecting tools that organizations already own, with room to change the processes around them.
Against large integrators such as Accenture or Capgemini, Krasan presents itself as a boutique with sector familiarity and personal access. Regional implementation firms and staffing specialists are alternatives too. Its clearest market fit is an institution with several connected problems: aging applications, awkward handoffs, staffing gaps, and employees whose working knowledge must survive the upgrade.
People are part of the architecture
President and CEO Pavithra Karumuri’s background includes application development, design, and business analysis. Dinkar Karumuri, who leads corporate strategy, brings enterprise planning and integration experience. Their biographies help explain the pairing of operational questions with technical execution. The company describes government, education, and finance as specialties, and says it has served hundreds of organizations across public and regulated sectors.
There is some evidence behind its emphasis on people. Great Place To Work’s profile, updated in February 2026, reports 273 U.S.-based employees and an 89% positive workplace response. That measures employee sentiment, not implementation quality. Still, in a business that sells expertise through teams, the experience of those teams is relevant. Krasan also appointed Steve Peralta in 2024 to lead client engagement in state, local government, and education.
Inc.’s 2026 Midwest Regionals lists Krasan at No. 25. A growth measure, not a disclosed revenue total.
Read the contract before the headline
Public procurement offers a useful glimpse of the buying process. A July 2024 Port of San Diego board paper recommended Krasan and three other vendors for as-needed technology and information-security staffing agreements. Staff reviewed 94 responses, interviewed eight firms, and recommended four. The proposed five-year aggregate ceiling was $7 million across the group. A shared ceiling establishes purchasing capacity; it does not establish Krasan’s revenue.
For a buyer, the distinction matters. Implementation work, ongoing support, and temporary staffing solve different problems and need different scopes. A sensible brief names the systems involved, the people responsible for data, the testing work, and who owns the result after launch. That checklist follows directly from the concrete deliverables in Krasan’s cases.
The approach also asks something of the client. As a practical inference, connecting systems and changing workflows requires access to staff, usable data, and time to settle disagreements. A buyer seeking a simple application with immediate setup may need a smaller intervention. Krasan’s cases concern organizations with existing machinery worth understanding. The task is to make that machinery easier to run, including on the ordinary Tuesday when nobody from the project team is in the room.