Current state map
A clear view of the workflow, systems, people, and handoffs in scope, including the places where the process changes in practice.
IT & Business Systems Assessment
Find out what is causing the problem before committing to a project.
KGS calls this engagement a Systems Review. It is a paid assessment with a fixed fee for important technology or workflow problems that are too unclear to scope responsibly.
KGS looks at how the work actually happens, where it breaks down, what the current technology and providers are doing, and what should happen first.
The result is a practical set of findings and next steps the client can use whether KGS performs the implementation or not.
When an assessment makes sense
Use an assessment when the problem is real but the answer is not obvious.
An assessment is useful when leadership is ready to address an issue but does not yet have enough information to choose a tool, approve a project, hold a vendor accountable, or decide what should happen first.
- The same operational problem keeps returning and several people or providers are involved.
- Leadership is considering a new system and wants to understand the current workflow before selecting or configuring it.
- A manual process is consuming too much staff time, but the business does not yet know whether the answer is process change, integration, automation, or something else.
- Reporting is slow or hard to trust because information comes from several places.
- An existing vendor relationship is stuck in a blame cycle and the business needs an independent view of the whole issue.
- An automation or AI initiative is being considered and leadership wants to know whether the process, data, controls, and expected value are ready for production use.
- A leadership change, growth period, or upcoming implementation has made undocumented dependencies harder to accept.
What KGS looks at
The assessment follows the work, not a generic audit checklist.
The exact scope depends on the question being answered. KGS may interview the people doing the work, review process documents, inspect relevant configurations, look at sample reports or records, and clarify where internal teams and vendors are responsible for different parts of the process.
Access is agreed in advance and should be limited to what the assessment actually needs.
- The current workflow, including common exceptions
- The applications and configurations involved
- Where information enters, changes, or has to be entered again
- Approvals, handoffs, ownership, and escalation
- Reporting and how leaders currently establish status
- Documentation and process knowledge
- Vendor responsibilities and dependencies
- Access, security, or data handling constraints relevant to the work
What you receive
You leave with something you can use.
The exact depth varies by scope, but the assessment is expected to produce a practical record of what KGS found and what leadership can decide next.
Issues and dependencies
A prioritized record of recurring failures, manual work, ownership gaps, risky dependencies, and unanswered questions that affect the result.
Quick fixes
Changes worth making now because they carry little risk, are well understood, and do not depend on a larger redesign.
90 day priorities
A practical sequence for the most important work, including what needs to happen first and what can wait.
Implementation options
A comparison of reasonable paths forward, including when the existing tools are sufficient and when a larger change may be justified.
Measurement plan
A small set of measures that will show whether the change improved the operation rather than merely producing a new deliverable or dashboard.
Fictional example. Not a client case study.
View the sample assessmentView an illustrative assessment.
How the assessment works
The work usually moves through four practical steps.
- 01
Scope the question
Agree on the business issue, the workflow or systems in scope, who needs to be involved, what access is appropriate, and what decision leadership needs to be able to make at the end.
- 02
See the work
Talk with the people doing the work and inspect the relevant systems, documents, reports, handoffs, and exceptions. The goal is to understand what happens in practice, not just what the process is supposed to be.
- 03
Put the picture together
Map the current process, test the obvious explanations, identify the important issues, and separate urgent fixes from changes that need more planning.
- 04
Review the decisions
Walk leadership through what was found, answer questions, explain the recommended order of work, and discuss who is best positioned to carry out each next step.
Why the assessment is paid
The assessment is real project work.
A useful diagnosis requires interviews, inspection, mapping, testing assumptions, and writing material the client can use afterward. Treating that work as free sales discovery would either make the assessment superficial or make KGS perform substantive consulting before there is an engagement.
The fit call is free because its purpose is simply to determine whether KGS and the situation are a sensible match. The assessment is paid because it produces work and recommendations that belong to the client and have value independent of a later implementation sale.
What happens afterward
The assessment does not automatically lead to another KGS project.
A useful assessment may show that no larger project is needed. It may identify work an internal employee or existing vendor should do. It may support a focused KGS implementation. In some cases, the business may want KGS to remain involved through ongoing support or stewardship.
The point is to improve the decision, not to manufacture an upsell.
What a client needs to provide
The assessment works best when KGS can see the real process.
A client needs an accountable sponsor, access to the people who actually perform or support the work, and permission to inspect the information reasonably required for the agreed scope.
That might include process documents, reports, sample records, system settings, contracts, vendor context, or interviews. KGS will agree what is needed before collecting it. Passwords and credentials should never be sent through the public website form or ordinary email.
FAQ
Questions about the assessment.
Do I need an assessment for ongoing IT support or a defined project?
No. If the need is clear enough to scope directly, KGS can discuss the support arrangement or project without an assessment. The assessment is for important problems where the cause or the right project is not obvious yet.
Is the first call free?
Yes. The first call is a short fit conversation. It is used to understand the situation at a high level, confirm that the right people are involved, discuss timing and access, and decide whether an assessment is worth proposing. It is not a free version of the assessment.
How much does the assessment cost?
The assessment has a fixed fee. KGS sets the fee after the fit call because the effort changes with the number of workflows, systems, locations, stakeholders, access requirements, and security constraints involved. The proposal states the fee, scope, and deliverables before work begins.
Does KGS have to implement the recommendations?
No. The assessment materials belong to the client. The next step may be no project, work by internal staff, action by an existing vendor, a focused KGS implementation, or ongoing support.
Can the assessment cover an AI or automation idea?
Yes, when the business question is larger than which tool should we buy? KGS can examine whether the workflow is stable enough to automate, what data is involved, what errors matter, who would review or override the result, and how success would be measured.
Do you need access to sensitive data?
Not automatically. KGS looks for the smallest useful set of information. In many cases, redacted records, samples, metadata, configuration views, or interviews are enough to answer part of the question. Any access to sensitive material should be agreed as part of the scope and handled under the applicable engagement terms.
What if the assessment shows our current software is fine?
Then that is useful information. The recommendation may be to configure the existing software differently, change ownership, simplify the process, improve documentation, or ask an existing vendor to make a specific change. An assessment does not need to create a new technology project to be useful.
Describe what keeps happening and why it matters now.
KGS will determine whether a short fit call is the right next step.