Useful answers, without the mystery

Good questions make for better products.

A few practical details about starting, building and looking after a product with ForgeLayer Studio.

Frequently asked

Planning the work together.

Where should we start if we only have a messy process and a rough idea?

Start with the work as it is today: who is involved, where decisions slow down, and what happens when something goes off the expected path. We can begin with a discovery sprint to map that reality, identify the highest-value opportunity and recommend a sensible first release. You do not need a polished brief.

How long does a project usually take?

It depends on the uncertainty, scope and integrations involved. Focused discovery often takes two to four weeks. A defined first product release may take a few months, while a larger platform evolves through staged releases. We share assumptions, milestones and decision points before committing to delivery.

How do you approach budgets and estimates?

We first agree the outcome and constraints, then estimate work at a useful level of detail. For a fixed-scope release, we document what is included, dependencies and how change is handled. For ongoing partnerships, we agree a team shape and monthly capacity, then make trade-offs visible as priorities evolve.

What happens during product discovery?

We speak with the people who do and depend on the work, observe the current service where possible, map workflows and system boundaries, and test key assumptions with lightweight prototypes. The result is a clear problem definition, evidence-backed priorities and a practical recommendation—not a long report that sits on a shelf.

Who owns the design and software you create?

After agreed project fees have been paid, the client owns the bespoke deliverables created specifically for the project, subject to the terms in our agreement. We retain ownership of our pre-existing tools, methods and reusable components, and grant the usage rights needed for the finished product.

Can you integrate with the tools and systems we already use?

Usually, subject to the available interfaces, access, security constraints and quality of the existing data. We map dependencies early, confirm what each system can safely exchange and design clear handling for failures. We do not assume that every tool needs to be replaced or connected.

How do you make accessibility part of the product?

We include accessibility in research, design review and quality assurance—not as a final visual check. Our teams consider keyboard access, focus order, semantic structure, readable contrast, clear content and assistive-technology behaviour. We agree relevant standards and testing depth with each client.

What support do you provide after launch?

We plan handover and support around the product and its operating needs. Depending on the agreement, this can include a stabilisation period, incident triage, product questions and a route for change requests. Current clients can use the dedicated support page for categories and published UK support hours.

Do you maintain products after the first release?

Yes. We can continue as a long-term product team or help your in-house team take ownership. Maintenance may include dependency updates, monitoring improvements, reliability work, security fixes and experience improvements. We agree responsibilities and response expectations in writing.

What security practices do you follow?

We use proportionate security practices throughout delivery: least-privilege access, careful handling of client data, code review, dependency awareness and explicit treatment of sensitive information. Architecture, hosting, retention and assurance requirements vary by product, so we confirm them with your security stakeholders early.

Can ForgeLayer work alongside our in-house product or engineering team?

Absolutely. We can join an existing team for a defined capability, bring specialist discovery or design support, or take shared responsibility for a product release. We align on ways of working, decision ownership, tooling and knowledge transfer so the partnership adds capacity without creating a separate island.

How does international collaboration work?

We work remotely with teams across time zones and plan collaboration deliberately. Workshops are scheduled with participants in mind, decisions are documented clearly and asynchronous reviews are part of the process. We agree overlap hours and communication channels before work begins.

Do we need to replace our existing software?

Not necessarily. A good solution may be a new interface around an existing system, a focused integration, a gradual replacement of one brittle component or a process change. We recommend the smallest effective intervention that supports the outcome and can be maintained.

What do you need from our team to make a project successful?

We need access to people who understand the work, a clear decision owner and time for timely reviews. Your team’s knowledge is essential: we bring facilitation, product design and engineering, while you help us understand context, validate decisions and prepare the organisation for change.

Still working through a specific question?

Talk it through