Service01
System and business analysis
We write down what your business needs and what the system has to do to deliver it. The result is a set of documents you can build from, procure from, and decide on.
MentiSec OÜ — Tallinn, Estonia
Clarity for complex
systems,
Clarity for complex
systems,
security from day one.
Clear thinking. Solid systems. A secure future.
System and business analysis, integrations and software development for Estonian businesses and the public sector. Clear, flexible, pragmatic.
01 — Who we work with
Starting points differ, but the expectation is the same: less mess, more confidence.
Public sector
Public-sector and adjacent projects
Analysis, integration, and security-requirements support for projects where precision and traceability matter.
Businesses
Both smaller and larger businesses
Messy processes, undefined requirements, manual data copying between systems — and the worry that one technical issue could halt operations.
Public procurement
Direct participation in public procurement
We take part in public procurements directly: analysis, integration and development work. One person is responsible from requirements to handover, and the scope is in writing before work begins.
02 — Recognised pains
If something here sounds familiar, you are not alone.
These are the four situations we hear about most often. First we make the picture clear, then we agree the next step.
Our processes have grown over years — nobody really knows anymore how things actually work.
Our responseAS-IS description, shared vocabulary, decision log — pressure off before anything is changed. System and business analysis →
We want a new system, but nobody has written down what it actually has to do.
Our responseRequirements documentation, user stories, TO-BE processes — the tender gets a concrete basis. System and business analysis →
Data is copied between systems by hand, and nobody remembers anymore where the original lives.
Our responseData-flow mapping, integration pre-analysis, API specifications. System integration →
A client or a contracting authority asks about security requirements, and we don't know what actually applies to us.
Our responseSecurity requirements as part of the requirements set, a risk and gap overview — no scaring, no overselling. Turvalisus äriettevõttes → (article in Estonian)
03 — What we offer
Three services that work together.
Every service has a page of its own, with deliverables, examples and starter packages — all services on one page →
Service02
Software development
We take the work from requirements to a working solution, and from analysis through to handover one person is accountable. The code lives in version control, and changes go through review and automated tests.
Service03
System integration
We get your systems exchanging information: data flows, interface descriptions, and the build itself. Every interface gets a description precise enough to run it years later.
See also: System replacement and data migration · Software testing · Terms of reference and procurement preparation
Every engagement ends with concrete deliverables that can be handed to a developer, leadership, an auditor or the next analyst — see all twelve deliverables →
08 — Anonymised examples
A few situations we work on.
Real client examples will appear here once the first projects have concluded and permission is in place. Below are typical situations.
Public sector
Integration analysis
Challenge
A public-sector institution needed to integrate a new national system with two legacy databases, but the precise data model had blurred over the years.
Approach
Data-flow mapping, shared vocabulary, initial requirements brief for the developer, security-aware view on access.
Result
The tender received a clearer technical brief; later development stayed within the agreed scope and timeline.
SME — logistics
Systems clarity audit
Challenge
A Tallinn company, ~40 staff, ran five separate systems with manual copying between them. A key person was about to leave.
Approach
Two-week audit: AS-IS processes, critical dependencies, risk areas. Short presentation to the owner.
Result
A clear three-step plan for the next year; one integration turned out to be unnecessary.
09 — Experience built at
Experience brought along, not written up.
The founding analyst has 13+ years of system-analysis practice in banking, telecom, IT consulting and logistics. That background leaves habits that don't disappear: precise wording, traceable decisions, documentation that stands up to scrutiny.
The founder's previous employment — not MentiSec client relationships.
13+years of system-analysis practice
10 — Why MentiSec
Three things that make a difference.
i.
One person responsible, start to finish
The same analyst takes the work from the first conversation to handover — nothing is lost along the way. When volume increases and time is tight, we bring in our professional collaboration partners.
ii.
Bridge between business and IT
We talk to both in one language. The client understands what is being done; the developer understands what is to be built.
iii.
Security from the start
Security awareness is part of requirements, processes and data flows from the start — part of every engagement, not a separate service or a line on the invoice.
11 — Founder
Marko Hartikainen
Founder, principal analystSystems analyst with 13+ years in banking, telecom, IT consulting and logistics. MentiSec is built on the conviction that a system change succeeds when someone is on your side from start to finish.
— END —
If it seems we could be useful — let's talk.
We talk through your situation and clarify which problems need solving and which opportunities are worth acting on. Afterwards we send a written summary, an initial work plan, and a proposal. All of this is free.
Email[email protected]
LinkedInin/markohartikainen