BrightNet Technologies Book a call

Engagement

The same process, whether it's a two-day audit or a multi-month rebuild.

Four stages, in order, every time. Nothing gets implemented that wasn't designed, and nothing gets designed that wasn't assessed first.

01 — Assess 02 — Design 03 — Implement 04 — Support
01
Assess
2 days – 1 week
02
Design
3 days – 2 weeks
03
Implement
1 – 8 weeks
04
Support
Ongoing
01

Assess

On-site or remote review of what's running, what's fragile, and what's actually at risk — documented, not assumed.

Typically 2 days – 1 week

What happens

  • ＋Walkthrough of network, systems, and security controls as they exist today
  • ＋Conversations with whoever actually touches the systems day to day
  • ＋Review of prior incidents, outages, or near-misses
  • ＋Risk is ranked by likelihood and impact, not by what's easiest to fix

What you get

  • ＋A written findings summary in plain language
  • ＋A current-state diagram, if one didn't already exist
  • ＋A go / no-go recommendation before any design work is quoted
No obligation — some assessments end here, with a report and nothing further to buy.
02

Design

A written plan with cost, sequencing, and trade-offs, so you're deciding on options instead of approving a black box.

Typically 3 days – 2 weeks

What happens

  • ＋Findings from the assessment are turned into concrete options
  • ＋Trade-offs — cost, downtime, complexity — are laid out for each option
  • ＋Hardware, software, and licensing needs are specified, not estimated
  • ＋A maintenance window and rollback plan are set before anything is bought

What you get

  • ＋A written design document with a bill of materials
  • ＋A fixed-scope quote for implementation
  • ＋A cutover plan you sign off on before work begins
You approve the plan — implementation doesn't start until the design is signed off.
03

Implement

Changes staged and tested before cutover, with a rollback plan for anything that touches production.

Typically 1 – 8 weeks, scope-dependent

What happens

  • ＋Configuration and staging happen off-hours wherever possible
  • ＋Cutover follows the window agreed on during design — no surprise changes
  • ＋Each change is verified before moving to the next
  • ＋Rollback is executed immediately if a step doesn't verify clean

What you get

  • ＋Status updates at each milestone, not just at the end
  • ＋As-built documentation reflecting what was actually deployed
  • ＋A post-implementation verification pass
Direct contact throughout — the person who designed it is the one implementing it.
04

Support

Direct access to the person who did the work — not a support desk that has to read your file first.

Ongoing, structured around your needs

What happens

  • ＋A defined warranty period on implementation work
  • ＋Documentation handed off so you're never dependent on one person's memory
  • ＋Optional standing advisory time for anything that comes up after

What you get

  • ＋A single point of contact for follow-up questions
  • ＋A documented response window, agreed on up front
  • ＋The option to convert to a standing advisory arrangement
No forced retainer — ongoing support is offered, never required, to close out an engagement.

During the engagement

The same three commitments apply across all four stages, regardless of engagement size.

Response time

A stated window, in writing

Every engagement sets a response window up front — you know how fast to expect an answer before you need one.

Change control

Nothing changes silently

Anything that touches production is scoped, scheduled, and confirmed with you before it happens — no surprise maintenance.

Documentation

Handed off, not held back

Diagrams, configurations, and credentials are documented and given to you — the engagement doesn't create a dependency on us.

Common questions

A few things that usually come up before an engagement starts.

How long does an engagement take?

It depends on the stage of work. An assessment alone can close out in a few days; a full network rebuild carried through implementation can run several weeks. Timelines are set during the design stage, not guessed at up front.

Do we have to commit past the assessment?

No. The assessment is scoped and billed on its own, and some engagements end there with a findings report and no further work.

Will you work alongside our existing vendors?

Yes. Most engagements involve coordinating with an ISP, a line-of-business software vendor, or another contractor already in place — that coordination is part of the design and implementation stages, not an extra.

What happens after implementation is done?

A defined warranty period covers the work itself. After that, support is available on request or as a standing advisory arrangement — it's never a requirement to close out the project.

Who actually does the work?

The person who runs the assessment and writes the design is the same person who implements it. Nothing gets handed off to a subcontractor you haven't met.

Start with an assessment.

A short call to understand what's running today and where the real risk sits — no obligation to continue past that.

Book a call