How we work & how we charge
Predictable budgets. Flexible delivery.
Most software projects evolve. New requirements emerge. Priorities change. Better ideas are discovered during development.
That is why Syngis uses a delivery model designed around predictable monthly investment and continuous progress — giving you budget certainty without sacrificing flexibility.
Monthly investment
Fixed amount. Agreed in advance.
Weekly capacity
Development hours for your project.
Continuous delivery
Work ships regularly, not all at the end.
Working software
Real progress. Visible outcomes.
Predictable
Monthly cost
Flexible
Priorities
Regular
Reviews
Continuous
Progress
Development capacity planner
Choose your monthly development capacity
Select the level of ongoing development support that suits your business. Each option gives you agreed development capacity, predictable monthly invoicing and regular progress without open-ended hourly surprises.
+ VAT per month
Per week
~hrs
Per month
hrs
Based on £65 + VAT / hour · All prices exclude VAT
Monthly hours are agreed in advance and used to plan delivery capacity. Final scope, priorities and availability are confirmed before work begins.
All options include
- Ongoing support via Microsoft Teams during office hours, Monday to Friday
- Azure DevOps Boards for task tracking and priorities
- Azure DevOps Pipelines for controlled deployments where applicable
- Source control and version-managed development
- Regular progress updates
- Priority planning and backlog review
- Code review and maintainability checks
- Testing and validation of completed work
- AI-assisted development where appropriate, with human review and accountability
- Documentation of important changes
- Deployment support for agreed releases
- Monthly summary of completed work and next priorities
Not included by default
Hosting costs, third-party licences, paid services, emergency out-of-hours support and major infrastructure costs are quoted separately where required.
The Syngis approach
A fixed monthly model with agreed weekly capacity
We agree how much development capacity is right for your project, set a weekly cap, and invoice a fixed monthly amount on a recurring basis until the project is complete.
This works especially well for bespoke business software, e-commerce systems, integrations, application modernisation and long-running development projects where the detail naturally evolves over time.
Your monthly development rhythm
Weekly capacity
Development hours allocated to your project, agreed in advance.
Monthly invoice
One fixed amount. No surprises.
Regular reviews
Progress visible, priorities adjustable.
Flexible priorities
Adapt as the project evolves.
Continuous progress
Work ships regularly. Nothing sits idle.
You get predictable spending.
We get the continuity needed to deliver properly.
Why this works for clients
Budget certainty without locking the project in place
A fixed monthly model helps business owners plan properly. You know your monthly development cost in advance — and you are not locked into a rigid specification that becomes outdated as soon as the project starts.
Predictable monthly budgeting
You know what you are investing each month, which makes planning and cash flow easier.
Flexibility as priorities change
This model allows the focus to adapt without starting a new commercial negotiation every time.
Continuous momentum
The development team keeps moving. Work does not stop while new quotes or change requests are prepared.
Better use of budget
More of your investment goes into building and testing software — not managing paperwork and scope disputes.
Clearer decision making
Regular progress reviews help you decide what matters next, based on what has been learned.
Long-term project knowledge
The same team stays close to your systems and business logic. That continuity matters with complex software.
Comparing approaches
Why we do not usually recommend rigid fixed-price development
Fixed-price software projects can work when the scope is small, clear and unlikely to change. But many bespoke software projects do not fit that pattern.
Rigid fixed-price project
- Inflated quotes to cover unknown risk
- Detailed assumptions that quickly become outdated
- Expensive change requests for anything new
- Delays while new work is re-scoped
- Friction over what is and isn't included
- Pressure to cut corners to protect the original budget
- A final system that matches the document, not the real business need
Fixed-price work is not always wrong — it suits small, well-understood, stable-scope projects well.
Syngis fixed monthly delivery
- Fixed monthly cost agreed in advance
- Priorities can adapt as the project develops
- No expensive change requests — just re-prioritise
- Work continues without commercial delays
- Focus on building the right thing, not protecting a document
- More budget spent on software, less on administration
- A system built around how the business actually works
Model comparison
Why not open-ended hourly billing?
Pure hourly billing can offer flexibility, but it can make budgeting harder — and can leave business owners nervous about every change, meeting and small decision. Our model keeps the flexibility of hourly development but adds a clear monthly structure around it.
Fixed price
Open-ended hourly
Syngis fixed monthly
RecommendedBudget predictability
Fixed if scope holds
Varies each month
Fixed monthly amount
Flexibility
Low — scope is locked
High but unpredictable
High within agreed capacity
Change handling
Expensive change requests
Discuss and bill as-go
Adjust priorities each cycle
Project momentum
Can stall at scope disputes
Depends on billing comfort
Continuous — no re-quoting
Best suited for
Small, clear, stable scope
Ad-hoc support work
Bespoke, evolving software
Visibility and communication
Weekly visibility. Monthly predictability.
A fixed monthly model only works if communication is clear. That is why we keep clients close to the work.
You should understand what has been completed, what is being worked on, what is coming next and where the main risks or decisions are.
You should never feel like development is disappearing into a black box.
Next priorities
Reporting layer
Email notifications
Monthly capacity
68% used · 32% remaining
AI-assisted delivery
Faster delivery without removing human accountability
We use modern AI tools to support parts of the software development process — helping us move faster through repetitive or time-consuming work such as understanding legacy code, supporting documentation, assisting with testing and accelerating early implementation work.
AI-assisted. Human-accountable.
We do not blindly ship AI-generated code. Production software is still designed, reviewed, tested and owned by experienced human software engineers. The value you are paying for is judgement, responsibility, architecture and long-term maintainability.
- Faster understanding of older systems
- Quicker prototyping and exploration
- Better support for documentation
- Assistance with test planning and coverage
- Reduced repetitive development work
- More time focused on important business logic
From legacy code to production-ready software
Legacy code
Existing codebase reviewed
Analysis support
AI assists code understanding
Documentation
AI helps generate docs
Tests
AI supports test planning
Human review
Engineers own every decision
Production-ready
Tested · documented · owned
We use AI to accelerate delivery — not to replace expertise.
What this means for your project
Predictable cost. Flexible priorities. Continuous progress.
It is not the cheapest possible way to buy software. It is a better way to control risk, maintain momentum and build systems that properly support your business.
A clear monthly development cost
A sensible weekly delivery capacity
Flexibility as requirements evolve
Regular visibility of progress
Less time spent on contract administration
Better continuity from the development team
A more realistic way to build bespoke software
Accountability for what gets built and how
Frequently asked questions
Common questions
Because many bespoke software projects evolve once development begins. A fixed monthly model gives you budget certainty while allowing priorities to adapt sensibly as the project develops.
No. The project still has direction, priorities and regular progress reviews. The monthly model controls spend while allowing the work to move forward without constant re-quoting.
Yes, where practical. If the project needs to move faster we can discuss increasing capacity. If priorities change or the pace needs to reduce, we can discuss that too.
Priorities can be reviewed and adjusted as the project progresses. This is one of the main benefits of the model — you are not locked into a specification that has become outdated.
Yes. The monthly amount is agreed in advance based on the development capacity allocated to your project. There are no surprise invoice spikes.
Yes. Ownership and licensing are agreed clearly before work starts. Our normal approach is to make sure clients understand what they own, what is being developed and how the system will be supported.
We provide regular communication appropriate to the project, including completed work, current priorities, upcoming tasks and any risks or decisions that need client input.
AI can help reduce repetitive work and accelerate parts of delivery, but we do not price projects simply by counting keystrokes. We price based on complexity, responsibility, business value and the quality of the outcome.
Let's discuss your project
Every project is different.
Some need a short, focused build. Some need ongoing development. Some need careful modernisation of older systems. Some need a long-term software partner who understands how the business works.
We can help you understand the likely effort, risks and delivery approach before you commit.
Conversation
Understand your system and goals
Proposal
Agree capacity and monthly investment
Delivery starts
Continuous progress from week one
Regular reviews
Priorities adapt as the project develops
Working software
Built properly. Owned by you.