Start with the right first question
Choose the ministry, security, enterprise or procurement route. No public project names or sensitive files are required in the first contact.
Next step: a short fit check to confirm path, scope and first deliverables.
Platform preview
Government operations platform
Signal 1
247 requests
Signal 2
31 overdue
Signal 3
96% auditable
Citizen service request
Directorate approval
Security site report
Performance trend
Start with a short institutional briefing
No public project names are required in the first contact. Choose the closest path, then turn the discussion into a pilot brief, technical pack or tender invitation.
Choose your situation and get the right route
You do not need to know the solution name or send sensitive files. Choose the closest situation, then start with a clear question or review route.
Ministry service pilot
Best for a citizen service, approvals, documents, complaints or dashboard that should start with one scope.
Start with a short, clear first contact
Share only the organization type, role, general problem and preferred contact method first. Do not send sensitive files in the first message.
Phone and WhatsApp
+964 785 333 2770
Location
Najaf, Iraq
Confidentiality
Confidential discussions are available under NDA when needed.
A clear path without unrealistic promises
Core-Intel reviews the request and responds through WhatsApp or email with the right next step: briefing, technical review, security survey or tender pack.
Core-Intel as a focused technology company
Three clear product directions make it easier for leadership, procurement and IT to understand where a first conversation belongs.
Digital government infrastructure
Citizen services, approvals, documents, complaints, appointments, inspections and leadership dashboards starting with one scope.
Request Ministry Pilot Brief
Enterprise operating systems
Branches, staff, finance, sales, suppliers, inventory, customer communication and management dashboards.
Request Enterprise Review
Government security technology
Site surveys, checkpoints, perimeters, command rooms, evidence reporting, field teams and incident timelines.
Request Security Site Survey
Each buyer should see a relevant reason to talk
The first conversation can be framed around what a minister, director, IT team, procurement officer or legal team needs to review.
For Ministers and leaders
Visibility over services, bottlenecks, policy impact and citizen experience without starting in technical detail.
For Directors-General
Control over ownership, overdue work, department performance, monthly reporting and operational accountability.
For IT departments
Review hosting, roles, backups, integrations, exports, monitoring and audit logs before delivery.
Open Technical Review
For Procurement
Clear scope, document pack, delivery phases, SLA model, maintenance, training and reviewable acceptance criteria.
Open Tender Pack
For Legal teams
Data ownership, confidentiality, access rules, handover, export, contract boundaries and public-reference control.
Start from the sector, not the application name
Each sector can start with one reviewable scope: service, approval, dashboard, archive, inspection or security workflow.
Municipalities
Citizen requests, complaints, permits, inspections, appointments and local-service dashboards.
View details
Healthcare
Appointments, complaints, facility inspections, service requests and health-directorate reporting.
View details
Higher education
Student services, committees, approvals, documents, appointments and academic dashboards.
View details
Courts and legal administration
Archiving, case administration, internal approvals, appointments, reporting and document governance.
View details
Transport and access points
Gates, permits, inspections, complaints, schedules, field follow-up and operations reporting.
View details
Finance and revenue
Requests, reviews, approvals, document matching, revenue reporting and ownership control.
View details
Security facilities
Checkpoints, perimeter, access, incident reports, evidence, field teams and command rooms.
View details
Energy and public assets
Sensitive sites, visits, permits, reports, maintenance, evidence and security follow-up.
View details
Public works
Projects, inspections, complaints, field visits, attachments and progress reporting.
View details
Administrative delay becomes operational cost
The problem is visible without exaggerated claims: paper, duplicate entry, unclear status and informal follow-up create avoidable friction.
Lost documents
When a request moves between offices without a clear record, teams struggle to know the correct version or last action.
Slow approvals
Without owner, status and escalation, approvals depend on manual follow-up instead of a visible process.
Weak audit trail
It becomes difficult to review who created, edited, approved, exported or closed a record.
Informal WhatsApp follow-up
WhatsApp helps coordination, but it is not enough as official archive, management dashboard or acceptance record.
Missing management dashboards
Without clear indicators, leadership cannot see request volume, delays, department workload or bottlenecks.
Choose the right document bundle instead of browsing every PDF
Three focused packs help leadership, procurement and IT review Core-Intel according to the discussion type.
Ministry Pilot Pack
For a ministry service, approval chain, document workflow or executive dashboard first scope.
Open ministry pack
Security Site Survey Pack
For gates, buildings, perimeters, checkpoints and command-room discussions that need confidential review.
Open security pack
Tender Due Diligence Pack
For procurement: eligibility, technical proposal, scope, SLA, implementation, acceptance and support model.
Open tender pack
What can be reviewed before any major commitment
These are not performance claims. They are examples of outputs that help leadership, procurement and IT make a decision.
Pilot brief
Problem, scope, roles, outputs, boundaries, assumptions and acceptance path.
Workflow map
Request steps, owner, status, escalation, documents and final decision.
Audit-log model
What is logged: creation, edit, approval, rejection, download and export.
Acceptance checklist
Checks for forms, roles, dashboards, documents, training and handover.
Training agenda
Admin, employee, management and IT training with operating documents.
Short answers to the most common reasons to hesitate
The goal is to reduce uncertainty before a formal meeting or tender invitation.
Can we start small?
Yes. The best start is one service, gate, branch or workflow.
Can the discussion stay private?
Yes. No organization or project names are published without written approval, and NDA handling is available.
Who owns the data?
The organization owns its data. Access, support and export rules are defined before operation.
Can IT review first?
Yes. IT can review hosting, roles, integrations, backups and audit logs first.
Are procurement documents available?
Yes. Tender pack, company profile, SLA model, implementation plan and acceptance criteria are available.
Is training part of delivery?
Admin, employee, management and technical handover training can be included in the delivery plan.
How we avoid an unclear project scope
Core-Intel starts with reviewable outputs: scope, acceptance, training, handover, support and an expansion decision.
What procurement can review first
Procurement can request early review material before sending formal files or finalizing tender scope.
Eligibility material
Company profile, contact information, services, confidentiality and participation readiness.
BoQ-style scope
Reviewable outputs, work units, assumptions, boundaries and exclusions.
Technical proposal and plan
Architecture, hosting, roles, integrations, testing, training and handover.
SLA, support and acceptance
Support model, maintenance, escalation, monitoring, acceptance criteria and sign-off points.
How IT and support teams can review operational readiness
Final commitments depend on contract and scope, but the operating model can be reviewed from the first technical conversation.
Monitoring and status
Review health checks, logs, alerts, status page and incident follow-up expectations.
Maintenance windows
Define maintenance scheduling, user communication and change documentation per deployment environment.
Escalation and support
Define support channels, priorities, escalation, monthly reporting and contracted response boundaries.
Backup and recovery
Review backups, isolation, exports, recovery and public or private hosting options.
Do not send sensitive documents in the first message
We only need the organization type, role, problem area and preferred contact channel first. Tender files or internal documents can be shared later through a confirmed formal channel.
Credibility without exaggeration or unsupported claims
Core-Intel should feel disciplined: clear about what can be reviewed, what depends on scope, and what is not claimed without documents.
Send the first request without sensitive details
A short intake form that captures organization type, request type, preferred channel and first scope without sensitive files.
Three clear actions instead of a generic contact request
Choose the action that matches the organization's current stage.