Web apps and portals built around how your customers work

Use 4–8 weeks as a guide for a small marketing website or 5–10 weeks for a focused customer portal. For web applications, allow 10–16 weeks for a fuller first release or 16–24 weeks for a defined complex initial scope; larger scopes can take longer. We agree the build cost and schedule around your scope and design approach, with hosting and support priced separately.

The examples cover kickoff through discovery, design, development, testing and initial handover. They assume available content and inputs, established interface components and a defined amount of integration work. We confirm responsibilities, dependencies and the milestone schedule during planning. Later phases and ongoing hosting or support are agreed separately.

Established interface components, adapted to your brand, are the baseline for the application examples. A custom design system adds work for bespoke screens, reusable components, visual rules and review. An existing design system can reduce that work. Advanced motion and interactions are optional additions that need their own development, performance and accessibility testing. We estimate the specific work rather than adding a fixed percentage.

We can build connections to systems such as your ERP, CRM, accounting software or payment provider. During discovery, we check the available interfaces, permissions and vendor requirements. The proposal sets out which integrations are included and any dependencies that could affect delivery.

Where content management is part of the scope, yes. We agree which pages, content types and reusable sections your team needs to manage, then provide the editing tools, permissions and training. Larger layout changes or new functionality may still need development, and we make those boundaries clear.

We agree performance and accessibility requirements at the start. Automated checks help catch issues during development, and manual reviews cover key tasks, keyboard use and screen-reader behaviour. We check the important pages and flows before launch and document any remaining limitations.

Yes. We review the code, hosting, content and integrations before recommending whether to improve, migrate or rebuild. If a migration is needed, we plan the content transfer, redirects, checks and cutover. We explain any expected interruption and the recovery plan before making the switch.

The domain and hosting accounts are set up in your company’s name. We recommend a hosting arrangement that fits the site’s needs and explain the provider charges and responsibilities. Setup and access are documented at handover. If we manage the hosting afterwards, that work is covered by the support agreement.

We hand over access and documentation, with editor guidance where content management is included. Ongoing support can cover CMS and dependency updates, monitoring, fixes and further development. We agree the coverage and fees separately, so it is clear what is included and what your team handles.