EditandoIdeas

Consulting

Before deciding what to do with a system, you need to know what state it is in.

We review code, architecture, technical security, performance and delivery processes, including Adobe Experience Manager implementations. It ends in a document with prioritized findings, not a sales pitch.

When it fits

Questions now argued with opinions.

An audit answers with evidence what is being argued today with opinions.

  • You inherited a system and nobody knows how it was built.
  • Every change takes longer than the last.
  • You are about to buy, integrate or replace a platform.
  • There are doubts about the security or stability of the system.
  • You want an independent opinion on a vendor’s work.
  • Your AEM implementation has become hard to maintain.

What it includes

What we review in the system.

  • Code

    Quality, readability, tests, dependencies and technical debt, with concrete examples from the repository.

  • Architecture

    Components, integrations and system boundaries, and where the risk is concentrated.

  • Technical security

    Access and secrets management, vulnerable dependencies, configuration and service exposure.

  • Performance

    Response times, resource usage, caching and bottlenecks with their likely cause.

  • Delivery processes

    Version control, code review, continuous integration, environments and deployment.

  • Adobe Experience Manager

    Components, templates, Dispatcher, content and governance of the implementation.

How we work

From access to remediation plan.

  1. Framing

    We agree on scope, the questions to answer and the access required.

  2. Review

    Analysis of code, infrastructure and processes, with team interviews.

  3. Findings

    Every finding with evidence, severity and a recommendation.

  4. Plan

    Actions ranked by risk and effort, grouped into phases.

  5. Handoff

    Presentation to the technical team and to the decision maker, with time for questions.

What you get

Evidence, risks and a plan.

  • Audit report with findings and evidence.
  • Prioritized risk matrix.
  • Diagram of the current architecture.
  • Phased remediation plan.
  • Executive summary for the decision maker.

FAQ

What people usually ask us.

What access do you need?

Read access to the repository and, depending on scope, to infrastructure and environments. Access is named and revoked when we finish.

Does the audit end in a proposal to rebuild the system?

No. It ends in a plan. If the conclusion is that your team or your current vendor can fix it, we say so.

Do you sign an NDA?

Yes, before we see any code or information.

Consulting

Other services in this discipline.

  • Project management

    Scope, schedule, and risks under control

    View service

  • SEO strategy

    Get found for what you actually do

    View service

  • Technology strategy

    Diagnosis, architecture, and roadmap

    View service

  • Corporate image strategy

    How your company looks and presents itself

    View service

  • Design consulting

    Experience, interface, and design systems

    View service

  • Brand positioning

    The place your brand holds and how to defend it

    View service

  • Technical support

    Care plans for a site already in use

    View service

  • Cloud consulting

    Infrastructure your team can run

    View service

  • Development consulting

    Hands-on support for your development team

    View service

Let’s find out the real state of your system.

Tell us which system it is and what decision is pending. The audit scope comes from there.

Tell us about your challengeEstimate the investment