Product engineering
Web applications and internal tools built from a clear specification, with a tested codebase and a deployment path that does not depend on any single person.
Software engineering & IT services
Considered software for organisations that depend on it
SMILE & GLOW STUDIO LTD designs, builds and maintains web platforms, internal systems and the infrastructure behind them. We work in small, accountable teams and write software that the people who inherit it can understand.
What we do
Our work covers the full life of a system: the discovery that defines it, the engineering that produces it, and the maintenance that keeps it dependable once it is carrying real traffic and real data.
Systems and integration
Connecting the software an organisation already runs — data sources, third-party services and internal APIs — so information moves without manual handling.
Operations and support
Cloud infrastructure, monitoring, backups and routine maintenance, arranged so that problems are noticed before they become incidents.
How we approach the work
We prefer to understand a problem before proposing a solution to it. That means reading the existing code, mapping the data, and asking what the system is actually expected to do once the current urgency has passed.
Decisions are written down. Technology choices favour maturity and documentation over novelty, because most of a system's cost is paid after the first release. Progress arrives in small increments against a running environment, so scope can be adjusted while adjustment is still cheap.
Our process
- Step 1
Discovery
We review the requirement, the systems in place and the constraints — technical, organisational and time-related — that will shape the solution.
- Step 2
Definition
Scope, sequence and architecture are written up in plain language, together with the trade-offs behind each significant decision.
- Step 3
Engineering
Work proceeds in short increments with automated tests and code review, deployed continuously to an environment you can see.
- Step 4
Handover and care
Documentation, deployment instructions and monitoring are delivered with the code, followed by maintenance where it is wanted.
Working with us
- Direct communication. You speak with the people writing the software, not through a layer of account management.
- Maintainable by design. Readable code, meaningful tests and written decisions, so the system survives a change of team.
- Realistic scope. We would rather narrow a plan early than deliver something broad and unfinished.
- Care for data. Access, retention and backups are treated as part of the engineering work rather than an afterthought.
Frequently asked questions
- What kind of projects does the company work on?
- Most of our work involves web applications, internal business systems, integrations between existing tools, and the infrastructure that keeps those systems running. Projects range from a focused improvement to an existing product to a complete build from an initial concept.
- How does a typical engagement begin?
- We start with a discovery conversation about the problem, the constraints and the systems already in place. From there we describe a scope, a sequence of work and the technical decisions we would recommend, so the first line of code is written against a shared understanding.
- Do you work with existing codebases?
- Yes. A large part of our work is inherited software that needs to be stabilised, documented and extended. We begin with a review of the code, the dependencies and the deployment process before proposing any changes.
- Which technologies do you use?
- We favour widely supported, well-documented technologies over novelty: standards-based web front ends, typed application code, relational databases and managed cloud services. The specific stack is chosen to match the problem and the team that will maintain it.
- How is progress communicated during a project?
- Work is delivered in short increments with a working environment available throughout. Written summaries describe what changed, what is next and any decision that needs input, so there is no gap between the state of the code and the state of the conversation.
- What happens after a project is delivered?
- Delivery includes documentation, deployment instructions and a handover of the environment. Where continued involvement is useful, we provide ongoing maintenance, monitoring and incremental development under a separate arrangement.
- How can the company be reached?
- Written enquiries can be sent by email to estherferguso59@gmail.com. Please include a short description of the project and any deadlines you are working towards.
Contact
Enquiries are handled in writing. Send a short description of the project, the systems involved and any deadline to the address below.
estherferguso59@gmail.com