Custom software development
Systems built around a specific operational problem rather than a generic template.
fourtimesonegroup.com / engineering group / est. index 4×1
Software built
the way it will
be maintained
FOUR TIMES ONE designs, builds, and maintains custom software, web applications, cloud environments, and integrations. Every engagement is documented, tested, and handed over in a state your own team can read.
- Discipline
- Custom engineering
- Language
- English
- Written contact
- consuelopowell199@gmail.com
- Practice areas
- Ten, listed
Figure 0 — engineering as a legible discipline, not a black box.
01Introduction
A small index of one idea, applied four ways
FOUR TIMES ONE is an information technology group. We work on software that organisations depend on daily: internal platforms, customer-facing applications, integration layers between systems that were never designed to talk to each other, and the cloud environments that run them.
The name describes the method. One problem, examined from four angles — the process it serves, the data it moves, the people who operate it, and the system that has to keep running afterwards. We do not start with a technology choice; we start with a written description of the problem and the constraints around it.
What we publish here is deliberately limited to what is true: the services we perform, the process we follow, and one email address to reach us at. No invented history, no counters, no claims we cannot support.
02 — Core capabilities
Four capabilities we keep in-house
- 1
Engineering
Implementation of software systems with version control, code review, and automated tests as standard, not as extras.
- 2
Architecture
Structural decisions written down with their trade-offs, so the reasoning survives longer than the meeting it came from.
- 3
Operations
Reproducible environments, automated deployment, monitoring, and recovery paths defined before they are needed.
- 4
Assurance
Functional, accessibility, performance, and security verification embedded in each delivery increment.
03Services
Ten practice areas, each with a defined scope
Full descriptions are on the Services page.
Web application development
Responsive, accessible web applications with predictable performance budgets.
Cloud solutions
Cloud environments described in code, so they can be reviewed and rebuilt.
Systems integration
Connecting existing systems without rewriting the ones that already work.
IT consulting
Technical assessment and planning before commitments become expensive.
Product engineering
Long-running engineering ownership for products that keep evolving.
Quality assurance
Testing designed as part of the system, not appended at the end.
Maintenance and technical support
Keeping delivered systems patched, observable, and understood.
Data and automation solutions
Turning repetitive process work into reviewable automated pipelines.
Cybersecurity-oriented engineering practices
Security treated as a property of the build process, not a final audit.
04Business areas
Sectors where the work fits
- Professional services
- Case, document, and billing workflows where accuracy and traceability matter more than volume.
- Logistics and operations
- Scheduling, tracking, and inventory systems that must stay consistent across several data sources.
- Manufacturing and industry
- Production reporting, machine data collection, and integration between shop-floor and office systems.
- Retail and commerce
- Catalogue, order, and fulfilment integrations between storefronts, ERPs, and payment platforms.
- Education and training
- Course delivery, assessment, and administrative platforms with strict accessibility requirements.
- Technology companies
- Engineering capacity for product teams that need architecture support or additional delivery throughput.
05Working process
Six stages, in order, every time
- 01
Framing
We write down the problem, the constraints, the people affected, and what would count as success. Nothing is estimated before this exists in text.
- 02
Technical design
Architecture, data model, integration points, and risks are documented and reviewed with your team so the plan is understood on both sides.
- 03
Increment build
Work is delivered in short increments with acceptance criteria, code review, and automated tests attached to each one.
- 04
Verification
Functional, accessibility, performance, and security checks run against the increment before it is considered done.
- 05
Release
Deployment is automated and repeatable, with monitoring, rollback paths, and release notes for the change.
- 06
Continuation
After release we maintain, measure, and extend the system, or hand over documentation so your team can operate it independently.
06 — Technology expertise
Tools chosen for the problem, not for the résumé
Languages and runtimes
- TypeScript
- JavaScript
- Python
- Java
- Go
- SQL
Web and interface
- React
- Node.js
- REST
- GraphQL
- Design systems
- WCAG 2.2
Data and storage
- PostgreSQL
- MySQL
- Redis
- Document stores
- ETL pipelines
- Reporting models
Cloud and operations
- Containers
- Kubernetes
- Infrastructure as code
- CI/CD
- Observability
- Backup and recovery
07Business benefits
What changes when the engineering is legible
Decisions you can audit
Architecture and trade-offs are written down, so a choice made months ago can be reviewed instead of guessed at.
Fewer surprises at release
Short increments with acceptance criteria surface misunderstandings while they are still cheap to correct.
Lower handover cost
Documentation, tests, and readable code mean your team can take over without a translation phase.
Operational visibility
Monitoring and logging are configured with the system, so behaviour in production is observed rather than inferred.
Contained technical debt
Known compromises are recorded with their cost, not left as undocumented folklore in the codebase.
Accessible by default
Interfaces are built to WCAG 2.2 AA expectations, which widens usable reach and reduces retrofit work.
08Security and quality
Verification is part of the build, not a stage after it
- Threat modelling at design time, with least-privilege access as the default posture.
- Secrets held in managed stores; never committed to source control.
- Dependency and vulnerability scanning wired into the delivery pipeline.
- Code review on every change, with automated tests required before merge.
- Input validation applied on both client and server boundaries.
- Accessibility and performance budgets defined before implementation begins.
- Findings logged with severity and remediation status rather than closed silently.
09Solution categories
Realistic shapes the work takes
These are categories of engagement, described generically. They are not case studies and contain no client information.
Cat. 01
Internal operations platform
Replacing a set of spreadsheets and manual handovers with one system that holds the process, the audit trail, and the permissions in a single place.
Cat. 02
Integration layer
A service that sits between a legacy back office and newer applications, translating data contracts and absorbing schema differences.
Cat. 03
Customer-facing portal
An authenticated portal where customers submit requests, follow status, and retrieve documents without contacting support by email.
Cat. 04
Reporting and data model
A consolidated reporting layer that collects operational data nightly, validates it, and exposes consistent figures to management tools.
Cat. 05
Process automation
Automation of a repetitive back-office routine, with validation rules, exception queues, and a log of every automated decision.
Cat. 06
Platform modernisation
Incremental migration of an ageing application to a maintainable architecture, keeping it in production throughout the transition.
10 — Collaboration
We work inside your process, in writing
Scope, assumptions, and open questions live in shared documents and issue trackers, so status is readable without a meeting. Reviews happen on increments rather than at the end, and decisions are recorded where they can be found again.
Where your team wants to take part in implementation, we pair on it and leave the conventions documented. Where they prefer to receive a finished system, we hand it over with the runbook attached.
11FAQ
Questions we are asked before starting
- What kind of projects does FOUR TIMES ONE take on?
- Custom software, web applications, cloud environments, systems integration, data and automation work, and long-running product engineering engagements. Scope is agreed in writing before work begins.
- How does an engagement usually start?
- With a written description of the problem and constraints. We review it, ask clarifying questions, and respond with our understanding of the scope, the technical approach, and the open risks before any implementation is planned.
- Can you work with an existing codebase?
- Yes. We begin with a review of the current architecture, dependencies, and test coverage, then agree which parts are extended, which are wrapped, and which are replaced.
- Which technologies do you work with?
- Primarily web and backend platforms, relational and document databases, containerised deployment, and mainstream cloud services. Technology choices follow the requirements of the system, not a fixed preference.
- How is quality verified?
- Through automated tests in the delivery pipeline, code review on every change, and defined acceptance criteria per increment. Accessibility and performance targets are stated before implementation so they can be measured afterwards.
- Who owns the resulting code and documentation?
- Ownership terms are set in the engagement agreement. Our standard position is that delivered source code and technical documentation belong to the client.
- How can we get in touch?
- By email at consuelopowell199@gmail.com. Written enquiries that include context, constraints, and timing are the fastest to answer usefully.
12Contact
Written enquiries only, answered in English
Describe the problem, the systems already involved, and any fixed constraints. Fuller details are on the Contacts page.
- Company
- FOUR TIMES ONE
- consuelopowell199@gmail.com
- Website
- fourtimesonegroup.com