FAQ / Useful answers

Good questions, answered plainly.

A few practical details about working with Morrowline. If the answer you need is not here, we are happy to talk it through.

Are we a good fit for Morrowline?

We are most useful when a complex workflow, customer journey or internal tool needs a clearer product answer—and your organisation can involve people who know the work. We work with established organisations as well as growing teams, provided the challenge and decision-makers are accessible.

How long does a project take?

It depends on scope and access to the people and systems involved. A focused discovery sprint commonly takes two to four weeks. A first product release may take several months. We define checkpoints and dependencies with you before committing to a delivery plan.

What happens during discovery?

We review the context, observe or interview people doing the work, map important journeys and constraints, then test assumptions that could change the solution. You receive a concise direction, options and a sensible next-step plan—not a large report for its own sake.

Do you choose a particular technology stack?

No single stack fits every organisation. We consider your existing systems, team capability, operational needs, integration constraints and likely maintenance before recommending a technical approach.

Will our organisation own the source code?

For custom software built under an agreed product engagement, source-code ownership and handover are set out in the proposal and contract. Third-party components remain subject to their own licences, which we identify and discuss.

How will our team collaborate with yours?

Your subject-matter experts and decision-makers join discovery, regular working sessions and demonstrations. We keep decisions visible in shared project materials and agree a communication rhythm that works across calendars and locations.

What support do you offer after launch?

We agree support arrangements, response windows and responsibilities in the engagement scope. Existing clients can use the Support page for project requests, production issues, administration and change assessment. We do not offer blanket 24/7 coverage.

How do you approach accessibility?

Accessibility is part of design and engineering decisions from the start: semantic structure, keyboard use, readable contrast, clear form feedback and testing with assistive technology where appropriate. We agree the relevant requirements for each product.

How do you handle security?

We discuss the data, access, hosting and operational risks specific to your context, then plan appropriate controls with your team and relevant specialists. We do not imply a certification or guarantee beyond the agreed scope.

What if the scope changes?

We record the change, discuss its effect on timing and cost, and agree what to adjust before starting the extra work. That may mean changing the sequence or replacing a lower-priority item rather than expanding everything.

Can you work with international teams?

Yes. We collaborate across locations using planned overlap, concise written decisions and recorded demonstrations where helpful. We agree working hours and decision routes at the start so time zones do not become a hidden dependency.

What does a first conversation cost?

The initial project conversation is a chance to understand the shape of the challenge and suggest a sensible next step. If a structured discovery or assessment is the right next move, we will outline its scope and fee before work begins.

Still wondering?

Ask us directly.

For a project question, use our enquiry page. Current clients can reach the right route through support.

Contact Morrowline ↗ Client support ↗