The approach
How we work on it
- Read the code, data model and hosting before forming an opinion.
- Describe the current structure and its main risks in plain language.
- Propose the smallest set of changes that makes the system safer to evolve.
- Record decisions and the reasons for them.
What you receive
Typical deliverables
- Architecture summary
- Risk register ranked by impact
- Recommended changes in order
- Decision record
What we will and will not promise
A review gives options and trade-offs. The decision stays with you, and we do not recommend a rewrite unless the evidence supports one.
How an engagement runs
Discover, propose, deliver, support
The same four stages apply to every Incipit practice, so you always know what has been agreed and what happens next.
- 01
Discover
We learn the business need, the people who will use the result and the constraints, before any solution is proposed.
- 02
Propose
Scope, milestones, responsibilities and ownership are agreed in a written proposal.
- 03
Deliver
Work is built in milestones. You review working builds and approve each stage before the next begins.
- 04
Support
Handover of code and documentation as agreed, with maintenance and support available afterwards.
Technology
What we build with
- ASP.NET MVC
- C#
- Entity Framework
- SQL Server
- Microsoft Azure
- Android (Kotlin)
- Bootstrap
Questions
Before you enquire
Related work
Where Incipit has done this
Related services
Describe what you need
Tell us the requirement and your time zone. We reply with questions, options and a written proposal.