//

You don't need to pick a fixed package.

Tell us what you want to solve and we'll define a workable scope before preparing a proposal.

Two ways to work together

Scoped project

We solve a concrete need — a website, an assessment, a review, an exercise — and the engagement ends with its delivery. You're not required to buy anything afterwards.

Talk about a project

Agreed follow-up

If there's a useful goal afterwards, we agree on reviews, priorities and capacity to support changes or verify fixes. We set the goal, coverage, cadence, exclusions, responsibilities and exit.

Talk about follow-up

From first message to proposal

  1. First conversation

    You tell us your goal and the general context. Please don't include passwords or sensitive information; this conversation doesn't authorize technical testing.

  2. Scope

    We define what will be done, what won't, the deliverables and who is responsible for each part.

  3. Proposal

    You get a written proposal for that scope. We don't publish prices or packages: each engagement is quoted on what it includes.

  4. Authorization and delivery

    Once authorization is signed we start the work, and at the end we verify what was agreed.

What you can expect

  • A web project can end with its delivery; it doesn't require pentesting or a later subscription.
  • The retest included in an assessment isn't billed again under another name.
  • If we assess something we also built, we say so.
  • No timelines or availability that haven't been agreed in writing.
See the eight services

Next step

Let's talk about what your organization needs

Tell us your goal and context. We'll define the next step and a realistic scope.

Talk to BALAM