Software studio with a project office · Bolton
Progress you can point to.
Enesy designs and builds mobile apps, websites and web systems, and runs them like well-kept programmes. Every fortnight you see something real, every risk has an owner, and every decision has a date.
Illustrative programme · weeks 1–12
Most software projects do not fail. They drift.
Drift is quieter than failure. Deadlines move by a week at a time. Decisions wait for a meeting that keeps being rescheduled. A feature grows because nobody wrote down where it was meant to stop. By the time anyone notices, the budget is spent and the product is half-finished.
Enesy exists to prevent drift. We combine a small software studio with the habits of a good project management office: a plan you can read, a rhythm you can rely on, a risk register that is actually used and a status report that tells the truth. The result is not more paperwork. It is fewer surprises.
Five workstreams, one plan
Draw a plan in thirty seconds
Choose a start date, the rough size of the work and how quickly decisions are made on your side. The planner draws an illustrative timeline with milestones, so you can see how decision speed changes the end date as much as scope does.
Choose a start date to draw an illustrative plan.
Illustrative plan only. Real plans are agreed after discovery.
The fortnight, every fortnight
Day 1
Plan
A thirty-minute planning session. We agree the outcome for the fortnight in one sentence and list what is in and what is not.
Days 2–9
Build
Design and development. You receive a short written update on Friday with a red, amber or green status and any decision we need from you.
Day 10
Show
A working build you can install or open, demonstrated live and then left with you to try. Feedback is captured against the plan.
After
Adjust
The plan is updated in the open. If a date moves, you see why and what we propose. Nothing changes silently.
Bolton roots, remote delivery
Enesy is registered in Bolton, in a town built on cotton mills where planning, sequence and dependable output were everything. We work remotely with organisations across the UK during London working hours, Monday to Friday, 09:00 to 18:00.
Illustration generated for this website. Not our premises.
Put a risk on the board
A risk register is only useful if it is short, visible and owned. Add the risks you are worried about and see where they sit on a likelihood and impact grid. High-high risks need an owner and an action this week.
Interfaces planned like everything else
Design at Enesy runs inside the plan, not beside it. Research interviews are scheduled in week one. Prototypes are tested in week two or three. Design decisions are logged with the same care as technical ones, so changes later are faster and cheaper.
We design to WCAG 2.2 AA from the first sketch: contrast, keyboard access, screen reader labels, sensible focus order and respect for reduced-motion settings. Accessibility issues are tracked as defects, not wishes.
Four gates, no ceremony
- Gate A: Scope agreed. A plain-English scope with in, out and later lists, plus an estimate range and its assumptions.
- Gate B: Design tested. A prototype has been tried by real users and the main issues fixed.
- Gate C: Ready to launch. Testing, accessibility checks, store or hosting preparation and a rollback plan are complete.
- Gate D: Handed over. Documentation, accounts, access and a support decision are in your hands.
Write a status report people read
The weekly update is the most important document in any project. Fill in the fields and the drafter produces a short, scannable report in the format we use ourselves.
Launch is a milestone with a checklist
App store submissions, privacy disclosures, screenshots, review notes, website DNS and certificates all have lead times. We put them on the plan from the start, so launch week is a confirmation rather than a scramble.
After launch, platforms keep changing their rules. Under support we track the changes that affect you and schedule updates before deadlines.
When a project is already drifting
Not every conversation starts at the beginning. Some organisations come to us halfway through: an app that has been “nearly ready” for two quarters, a website rebuild with no clear end, or a supplier relationship that has gone quiet. In those cases we start with a short recovery review. We read the code, the tickets, the documents and the contracts you can share, talk to the people involved and produce a written assessment within an agreed number of days.
The assessment answers four questions in plain English: where the work really is, what is blocking it, what it would take to reach a usable release, and whether continuing is the right decision at all. Sometimes the honest recommendation is to finish with the existing team and better governance; sometimes it is to stop and preserve what is useful. Either way you receive a plan you can act on, with or without us.
Templates you can use without us
- A one-page scope templateTemplate
- How to keep a RAID log usefulGuide
- The four-line status reportTemplate
- What a proper handover containsChecklist
Your project’s next milestone could be a conversation.
Tell us what you are building or rescuing. We reply during working hours with the questions we would ask at a kick-off and a view on whether we are the right team.