MONO/DEV

Our working process

How a project moves from requirements to launch: direction, proposal, content, customisation, review and handover with clear responsibilities.

1. Requirements and direction

Start with your activity, audience, required functions and available materials. If you have selected a catalogue project, we compare its demonstration with your requirements and record the differences.

2. Proposal and scope

We define the proposed pages, languages, adaptations and integrations. Cost, timing, usage rights, payment options and responsibilities are clarified before work begins.

A catalogue price does not imply that any new feature or external subscription is included. Those items need to be identified separately in the project proposal.

3. Content and customisation

Prepare real business materials: logo, copy, authorised photography and contact details. Your business validates specialist information such as clinical content, products or property data.

We adapt the screens and implement agreed functionality. New scope is assessed before it changes cost and schedule expectations.

4. Review before launch

We check the pages and important journeys, including navigation, mobile layouts, forms and links. Live integrations are tested using the access and environments available for the project.

The prepared version is reviewed before publication. Launch depends on required materials, access and approvals rather than a universal delivery time promised on this site.

5. Publication and handover

Publication, project access and handover documentation follow the agreed package. Maintenance tasks, responsibilities and support conditions are defined separately when required.

Discuss your project

monodev@gmail.com