How we work

A practical delivery process with clear accountability at every step

We run projects in seven steps, from understanding the problem to supporting the result. At each step you know what is happening, what you will receive and what we need from you. Small websites move through them quickly; business systems take longer.

The delivery process

Seven steps, each with a clear output

  1. Discovery

    We start with the business problem, not the technology: how work is done today, the systems and data involved, and constraints such as budget, deadlines and regulations. First conversations are free. Larger projects may begin with a paid discovery phase, agreed in writing first.

    You receive: a short written summary of what we understood, the options we see and the open questions.

    Your role: explain the goal, show us the current process and give us time with the people who know the work.

  2. Proposal and scope

    We turn discovery into a written proposal: scope, deliverables, assumptions, exclusions, acceptance criteria (the checks that show a deliverable is complete), timeline and commercial terms, including ownership and licensing.

    You receive: a proposal you can question and compare, priced on the agreed scope.

    Your role: review the scope closely, ask about anything unclear and approve it in writing before work starts.

  3. Design

    Before building, we design the workflows, data, architecture (how the parts fit together and where they run) and user experience, including security decisions such as who can see and change what.

    You receive: design material sized to the project, such as wireframes (simple screen layouts), workflow diagrams or an architecture outline.

    Your role: check the design against how your business really works, involve the people who will use it, and approve it or ask for changes.

  4. Build

    We build in short cycles and deploy work in progress to a test environment, a private copy kept separate from your live systems.

    You receive: regular demonstrations, access to the test environment and plain-language progress updates.

    Your role: attend reviews, try the work, give prompt feedback and supply content on the agreed dates. Late inputs move the timeline.

  5. Test and acceptance

    We test against the agreed acceptance criteria, including security checks suited to the project. Your team then runs user acceptance testing (UAT), trying the tasks they will do every day. We fix what fails and retest.

    You receive: a summary of what was tested and fixed, and any known issues with a plan for each.

    Your role: test with realistic scenarios, report issues clearly and confirm acceptance in writing.

  6. Launch and handover

    We deploy to the live environment at an agreed time, migrate existing data if that is in scope, and check that everything works. Then we train your team and hand over documentation, access and credentials as agreed.

    You receive: a working live system, training and the handover items listed in your scope.

    Your role: agree on the launch window, make people available for training and store handed-over credentials securely.

  7. Support and improvement

    Support, maintenance and hosting after launch follow the arrangement set out in your agreement, including support hours and response targets. Your proposal states any defect-fix period after launch. Our hosting and support page describes the options. New features go through change requests.

    You receive: support on the agreed terms and a clear route for requesting changes.

    Your role: report issues with enough detail to reproduce them and tell us early when your needs change.

Accountability

Who you work with

You work directly with our own team: experienced technical people who take responsibility for delivering your project.

Direct access to the people doing the work

You discuss your project with the people who design and build it, not an account manager passing messages along.

Responsibility for delivery

The people who agree the scope with you are responsible for delivering it. They coordinate the work, raise risks early and bring decisions to you.

Experienced people

The team brings 15+ years of hands-on technology experience. S3curity Net itself is a new company, founded in 2026.

More about S3curity Net

Handover

What you get at handover

Handover is part of the project, not an afterthought. A typical handover includes these items, as agreed in your scope.

What you own and what is licensed to you are set out in your agreement and explained on our ownership and licensing page.

  • Documentation for the people who use and administer the system
  • Administrator accounts for your team, with the access set out in your agreement
  • Deployment notes: where the system runs, how it is configured and how updates are released
  • Backup and restore notes: what is backed up, where, how often and how to restore it
  • Training materials for your users and administrators
  • A list of the domains, licenses and third-party services the system depends on, with renewal dates

Keeping a project on track

How we keep scope, cost and progress clear

Decisions in writing

Scope, design choices and changes are written down, so everyone works from the same version.

No surprises on scope or cost

Work outside the agreed scope goes through a change request showing its cost and timeline impact, and starts only after you approve it.

Plain-language reporting

Updates cover what is done, what is next and what needs your decision. Risks are raised early, not at the deadline.

The principles behind our work

FAQ

Questions about working with us

How does a project start?

Tell us what you need through our contact page or at hello@s3curity.net. First conversations are free. We then send a written proposal or, for a larger project, may suggest starting with a paid discovery phase, agreed in writing first. Nothing is billed until you approve it in writing.

How does pricing work?

Projects are quoted individually once the scope is agreed, because the price depends on what is built, the systems involved and the support needed afterward. Payment terms are set out in each proposal. For simpler websites, we offer three website packages with set inclusions, each quoted on request.

How long will our project take?

It depends on the scope, the systems involved and how quickly content, data and feedback arrive. Your proposal includes a timeline with milestones, and we tell you as soon as a date is at risk.

What do you need from us?

A decision-maker who can approve scope and design, a day-to-day contact, and access to the relevant systems, data and people. During the build: prompt feedback and content only you can provide, such as text, images or existing records. For launch: access to your domain, hosting or other accounts.

What if we need changes during the project?

Changes are normal. Feedback on work already in scope is handled in regular reviews. Anything new gets a written change request showing its effect on cost and timeline, and starts only after you approve it.

What happens after launch?

We check the system after go-live. Your proposal states any defect-fix period, and your agreement sets the support hours and response targets. From then on, support, maintenance and hosting follow that agreement, and new features are agreed as change requests or a new phase of work.

Who owns what you build for us?

Your proposal states what you own and what is licensed to you. Work built specifically for you, our own tools and products (H3lix, LIM5 and Sal3s), third-party software and your data are each treated differently, and our ownership and licensing page explains each case.

Ready to talk about your project?

Tell us what you want to achieve and what you use today. We will reply with questions and suggested next steps.