Loading your next page
Working with Cosilan
You should understand what is being built, what it costs and what happens next. These are the conversations we want a project to be built around.
Understand
Explain the task, the people involved and what gets in the way. We can discuss the options, including whether an existing tool already covers the need.
A shared problem to solve.Define
Separate the essentials from later ideas. Agree the scope, fees, dependencies and review points before project work starts.
An agreed scope and a basis for the estimate.Build & review
Agree how progress will be demonstrated and who will review it. Test the intended workflow, permissions and important failure cases against the scope.
Work reviewed against the agreed requirements.Handover
Set out deployment, documentation, account access and support responsibilities. Discuss how future changes will be requested and charged.
An agreed handover and plan for operation.Before you commit
A project agreement should turn these topics into specific responsibilities. The answers depend on the work you commission.
Agree what is included, which assumptions need checking and how changes are priced. Separate development fees from hosting, third-party subscriptions and ongoing support. A smaller first version may be a better use of the budget than building everything at once.
Understand software estimatesDiscuss ownership, source-code access, account control, third-party licences and documentation. Record the agreed terms in the project agreement, including what you receive at handover.
Discuss the reason for a deadline, the essential first release and dependencies such as access to existing systems. Agree how changes affect scope, price and delivery rather than leaving them implicit.
Our team writes the code and takes responsibility for the work. We review it against the agreed requirements and test the important workflows before handover. You can ask questions, review progress and discuss decisions directly with the people building your software.
Agree who manages hosting, backups, updates, support requests and future development. Support arrangements and response times must be set out for the project; they are not assumed to continue indefinitely.
Tell us what you want to improve. You do not need a complete specification to open the conversation.