Skip to main content
FOUR TIMES ONE logo: four amber squares in a rowFour Times One

Ten services, each with a scope you can hold us to

Every entry below describes work FOUR TIMES ONE performs. Deliverables and acceptance criteria are agreed in writing per engagement; we make no guarantees about outcomes we cannot measure.

  1. 01 — Custom software development
  2. 02 — Web application development
  3. 03 — Cloud solutions
  4. 04 — Systems integration
  5. 05 — IT consulting
  6. 06 — Product engineering
  7. 07 — Quality assurance
  8. 08 — Maintenance and technical support
  9. 09 — Data and automation solutions
  10. 10 — Cybersecurity-oriented engineering practices

Service descriptions

01

Custom software development

Systems built around a specific operational problem rather than a generic template.

We design and build software from requirements analysis through delivery: domain modelling, architecture, implementation, automated testing, and release. Work is organised in short increments so the system can be reviewed while it is still inexpensive to change direction.

  • Requirements analysis and domain modelling
  • Architecture and technical documentation
  • Incremental delivery with reviewable milestones

02

Web application development

Responsive, accessible web applications with predictable performance budgets.

We build browser-based products and internal tools: interface engineering, state and data flow, API layers, authentication, and role-based access. Accessibility and performance are treated as engineering requirements, defined up front and verified before release.

  • Component architecture and design systems
  • API design and data-fetching strategy
  • Accessibility and performance verification

03

Cloud solutions

Cloud environments described in code, so they can be reviewed and rebuilt.

We plan and implement cloud architecture, containerised workloads, and deployment pipelines. Infrastructure is expressed as code, environments are reproducible, and observability is configured so operational behaviour is visible instead of assumed.

  • Infrastructure as code and environment parity
  • Containerisation and deployment pipelines
  • Monitoring, logging, and cost visibility

04

Systems integration

Connecting existing systems without rewriting the ones that already work.

We map data ownership between systems, design integration contracts, and implement synchronisation with clear error handling and retry behaviour. Legacy interfaces are wrapped rather than replaced when replacement adds risk without adding value.

  • Interface and data-contract design
  • Event-driven and batch synchronisation
  • Error handling, retries, and reconciliation

05

IT consulting

Technical assessment and planning before commitments become expensive.

We review existing architecture, delivery practices, and technical risk, then document options with their trade-offs. The result is a decision record you can act on internally, not a dependency on us to interpret it.

  • Architecture and code review
  • Technology selection and trade-off analysis
  • Delivery roadmaps and risk registers

06

Product engineering

Long-running engineering ownership for products that keep evolving.

For products with an ongoing roadmap we operate as the engineering function: discovery, prototyping, iterative release, and technical maintenance of the codebase, with documentation kept current so knowledge does not live only in people's heads.

  • Discovery and prototype validation
  • Iterative roadmap execution
  • Technical debt and documentation upkeep

07

Quality assurance

Testing designed as part of the system, not appended at the end.

We define test strategy across unit, integration, and end-to-end layers, automate regression coverage in the pipeline, and add exploratory and accessibility testing where automation is a poor fit. Defects are tracked with reproducible cases.

  • Test strategy and coverage design
  • Automated regression in CI
  • Exploratory, accessibility, and performance testing

08

Maintenance and technical support

Keeping delivered systems patched, observable, and understood.

We handle dependency and platform updates, monitoring, incident response, and small change requests. Each intervention is logged so the operational history of the system stays readable to your team.

  • Dependency and platform updates
  • Monitoring and incident response
  • Change requests and release management

09

Data and automation solutions

Turning repetitive process work into reviewable automated pipelines.

We build data pipelines, reporting layers, and workflow automation: extraction, validation, transformation, and delivery into the tools people already use. Automated steps stay auditable, with clear ownership of the data at every stage.

  • Data pipelines and validation rules
  • Reporting and analytics models
  • Workflow and back-office automation

10

Cybersecurity-oriented engineering practices

Security treated as a property of the build process, not a final audit.

We apply threat modelling, least-privilege access design, secret management, dependency scanning, and secure code review inside normal delivery. Findings are documented with severity and remediation status rather than resolved silently.

  • Threat modelling and access design
  • Secret management and dependency scanning
  • Secure review and remediation tracking

Engagement shapes

Three ways the work is usually structured

Defined project

A bounded scope with documented requirements, milestones, and acceptance criteria agreed before implementation starts.

Continuous engineering

Ongoing capacity for a product with a live roadmap, delivered in recurring increments with regular review.

Assessment

A time-boxed review of an existing system or delivery process, ending in a written report of findings and options.

Deliverables

What arrives alongside the software

  • Source code in your version control, with readable commit history.
  • Architecture and data-model documentation kept current with the code.
  • Automated test suites runnable in your own pipeline.
  • Infrastructure definitions for each environment.
  • Release notes and a runbook covering deployment and recovery.
  • A written record of open risks and known compromises.
Isometric graphic of amber and rust blocks representing layered software services
Figure 1 — services as layers, not as a menu.
Hands sketching architecture diagrams on paper during an engineering planning session
Figure 2 — scope agreed on paper before estimation.

Contact

Enquiries about scope

Send a written description of the problem and constraints. See the Contacts page for details.

consuelopowell199@gmail.com