Questions before commissioning UK website or software work

Are you based in the United Kingdom?

Faith Forge Labs is based in the United States and delivers remotely. This site describes services for UK organisations; it does not establish a UK office. Communication, technical delivery and any support overlap are agreed around the people and calendars involved.

Do we need a complete rebuild?

A rebuild is one possible response, not the starting assumption. We examine the failed task, the condition of the existing application and the dependencies a replacement would inherit. A correction, content improvement or provider configuration may be enough. Read repair or replace for the decisions behind that comparison.

Can you take over something another developer built?

We can assess an existing system when the organisation has authority to provide the necessary materials and access. The scope depends on what is available: source code, deployment information, accounts, documentation and a safe way to investigate. Missing access can prevent a reliable estimate and may need to be resolved with the current supplier.

Can members edit their own information?

A portal can provide agreed self-service actions, but each field needs an owner and a rule. A contact preference may be editable immediately; an eligibility change may need staff review. We discuss what the member sees while a decision is pending and how staff correct mistakes without losing the history.

Can you connect our CRM or payment provider?

That depends on the provider's supported operations, the account and the permission available. We examine the actual interface and error handling before promising a connection. A reviewed import or a smaller manual step can be more appropriate when a dependable interface is unavailable.

Will a redesigned site be legally compliant or accessibility certified?

A development deliverable does not, by itself, establish either conclusion. We agree the accessibility objectives and testing scope, implement approved information-handling decisions and record remaining limitations. Your organisation determines applicable obligations with the qualified advice it needs. Official guidance is linked on the references page.

How much will the work cost, and how long will it take?

The answer depends on the task, existing condition, content, access and review requirements. We can discuss an initial boundary, then distinguish work that can be estimated from work requiring investigation. The scope guide explains what should be visible in a proposal, including third-party costs and exclusions.

Do we need to send real member records?

Usually not for an initial conversation. A fictional record can demonstrate a renewal, document correction or organisation change. Any later access to private information needs an appropriate purpose and arrangement. Please keep credentials and confidential files out of ordinary enquiries.

What happens if an important requirement changes?

We describe its effect on the agreed deliverable, cost, timing and tests before adding it. A wording correction is different from changing the rule that wording describes. Keeping that distinction visible helps your team decide whether to change the current release or plan another piece of work.

What do we receive at handover?

The agreed materials can include source or configuration, account responsibilities, operating instructions, checks and known limitations. Your staff should be able to identify how a routine task is done and who handles a failure. Ongoing support is discussed explicitly; it is not automatically included without limits.

What is enough to start?

A public link, a short explanation of the task and an example of where it fails. If you only have an idea, explain who would use it and what they do today. Contact us or use the brief builder to organise the questions.