ContactES

Project management services

Order the start, the control and the close

Orders the start, the control, the client relationship and the close. The service coordinates activities, milestones, risks, blockers and commitments. It does not execute the teams' technical work and it is not reduced to updating a board.

From

USD 1.500 One-off stage

Close: Formalizes the end of the project and the continuity of what stays open. Reference price, subject to scope validation.

Compare plans and pricesTalk to an advisor
  • 01
    Defined scope

    Each plan states what is included and where it stops.

  • 02
    Visible prices

    The reference amount is shown on every plan.

  • 03
    Validation first

    Scope is confirmed before the proposal.

01

Project management

Four components, each with its own perimeter. Follow-up is the base recurring service. The client relationship is added only as a complement.

See the detailed comparison

01

Start

One project, with the key counterparts and participants available

USD 2.000One-off stage

Structures the start. It does not execute the technical content.

  • Plan · Work
  • RACI · Governance
  • Kickoff · Start

02

Follow-up · Package 1

Up to 3 fronts, up to 4 teams or areas and up to 3 active dependencies

USD 1.800 / monthMonthly service

The same control function, for a bounded coordination structure.

  • 3 · Fronts
  • 4 · Teams
  • 3 · Dependencies

03

Follow-up · Package 2

4 or more fronts, 5 or more teams or areas, and/or 4 or more active dependencies

USD 3.000 / monthMonthly service

The same functional scope, with greater volume or interdependence.

  • 4+ · Fronts
  • 5+ · Teams
  • 4+ · Dependencies

04

Add-on

One client, with contacts and a relationship channel already identified

USD 750 / monthMonthly service

A management add-on. It is not a standalone service.

  • +1 · Add-on
  • 1 · Review
  • Channel · Needs

05

Close

One project ready to close, with owners available to confirm

USD 1.500One-off stage

Formalizes the end of the project and the continuity of what stays open.

  • Status · Final
  • RACI · Acceptance
  • Risks · Close

Choosing a plan shows its scope. Requesting it opens the contact form with that selection and does not confirm the purchase.

Selected plan

Initial planning

The project needs to start with activities, milestones, owners, priorities and a follow-up rhythm.

USD 2.000 One-off stage

Structures the start. It does not execute the technical content.

What is included

  • Review of available requirements and background.
  • Coordination with technical counterparts to identify the required activities.
  • Joint construction of the initial work plan.
  • Jira board setup, if required.
  • Project governance model: roles, authorities, sessions, escalation and a single-reference RACI.
  • Preparation and facilitation of the kickoff.
  • Initial alignment and a register of agreements and commitments.

Delivery: One-off payment, at the start of the project

It does not execute the technical work, it does not replace the specialists, it does not approve scope changes, and the close does not become later support.

Detailed comparison

Swipe sideways to see every plan.

StartFollow-up · Package 1Follow-up · Package 2Add-onClose
PriceUSD 2.000USD 1.800 / monthUSD 3.000 / monthUSD 750 / monthUSD 1.500
PaymentOne-off stageMonthly serviceMonthly serviceMonthly serviceOne-off stage
ScopeOne project, with the key counterparts and participants availableUp to 3 fronts, up to 4 teams or areas and up to 3 active dependencies4 or more fronts, 5 or more teams or areas, and/or 4 or more active dependenciesOne client, with contacts and a relationship channel already identifiedOne project ready to close, with owners available to confirm
ResultAn initial working base: plan, risks, agreements and the project's governance model.Control and coordination with executive visibility. It is not a Jira-update service.Control and coordination with executive visibility. It is not a Jira-update service.Relationship, perception and channelling of needs. It does not design or execute the solution to those needs.A formal close. It is not support, operation or permanent custody after the project.
DeliveryOne-off payment, at the start of the projectUp to 3 fronts, 4 teams or areas and 3 active dependencies4 or more fronts, 5 or more teams, or 4 or more dependenciesIt is added to planning and/or follow-upOne-off payment, at project close
IncludesReview of available requirements and background.Follow-up of the work plan, activities, milestones, pending items and blockers.Follow-up of the work plan, activities, milestones, pending items and blockers.Relationship management with the defined contacts and alignment of expectations.Check of the final status of the main milestones and activities.

Reference prices for the standard scope. The final scope is validated before the commercial proposal.

Before starting, it is written down which coordination is bought, which records are delivered and which decisions stay with the owners of the work.

02

What this service includes

Before starting, it is written down which coordination is bought, which records are delivered and which decisions stay with the owners of the work.

01

What you buy

One management component: start, follow-up, relationship or close. Follow-up is packaged according to fronts, teams and dependencies.

    02

    What you receive

    Plans, sheets, registers, minutes and visibility of progress, risks, blockers and commitments. Jira is used when the project needs it.

      03

      Where it stops

      It does not execute the technical work, it does not replace the specialists, it does not approve scope changes, and the close does not become later support.

      • Definition or execution of the project's technical content.
      • Replacing technical counterparts in estimates, validations or specialist decisions.
      • Execution of activities assigned to other owners.
      • Approval of requirements or scope changes outside Enterprise Management authority.
      • Execution of technical activities or of actions assigned to other owners.
      • Updating Jira tasks on behalf of their owners.

      03

      How it works

      Identify the moment of the project. Each situation opens the matching component, with its scope and its limit.

      1. 01

        Choose the level

        Pick the plan that matches the size and the decision you need to make.

      2. 02

        We validate the scope

        We confirm the starting point and the conditions of the published plan.

      3. 03

        We do the agreed work

        The work stays inside the scope of the plan you request.

      4. 04

        You receive the result

        You receive the deliverables defined for that plan.

      Before starting, it is written down which coordination is bought, which records are delivered and which decisions stay with the owners of the work.

      OpsAnalytics experience

      The service sets the next step.

      Published cases show how OpsAnalytics supports architecture, operations and the decisions that follow.

      View success stories

      04

      Frequently asked questions

      Conditions that change the decision to buy.

      What is a front, a team and a dependency?

      A front is an area with its own activities and owners, for example infrastructure or development. A team or area is a group that participates actively. A dependency exists when one team cannot move until another finishes something, for example enabling an environment.

      Why does follow-up have two prices if the scope is the same?

      Both packages include the full scope: control, coordination, risks, blockers, commitments, escalation and visibility. Package 1 covers up to 3 fronts, 4 teams or areas and 3 active dependencies. Package 2 applies from 4 fronts, 5 teams or areas, or 4 active dependencies. What changes is the intensity of coordination, not the list of functions.

      Can relationship management be bought on its own?

      No. It is a complement. It is added to a package that already includes initial planning and/or follow-up and control. It is not offered as a standalone service.

      Does the close include support after the project?

      No. It formalizes the final status, acceptance, pending items, risks that remain open and the handover. Operation, support or later follow-up exist only if they are contracted in another service.

      Is Jira mandatory?

      No. The board and the panels are configured or followed when the project needs them. The service does not consist of updating tasks on behalf of their owners.

      Does Enterprise Management execute the technical activities?

      No. It coordinates, follows up and escalates. Definition, estimation, execution and specialist validation stay with the technical, functional or client owners.

      Not sure which plan you need?

      Tell us about your starting point. We will help you identify the right plan and confirm its scope.