Frequently asked questions

Northbridge serves organizations in the United States that need practical improvements to operations, internal software, integrations, reporting, automation, or existing applications. Many are growing organizations with approximately 10–500 employees, but suitability depends more on the business problem, scope, and required capabilities than on a strict company-size rule.

Yes. Many engagements begin with existing SaaS tools, databases, internal applications, spreadsheets, APIs, or legacy software. The first step is understanding the current environment, access, data, ownership, constraints, and available integration options.

No. Work may include improving an existing application, connecting systems, automating a workflow, building a focused internal tool, improving reporting, stabilizing older software, or planning phased modernization.

AI is used selectively where it improves a defined workflow, such as document classification, data extraction, summarization, knowledge retrieval, assisted routing, or structured drafting. Appropriate access controls, exception handling, review steps, and human oversight remain part of the solution design.

An engagement begins with a discussion of the business objective, current process, existing systems, and desired outcome. Depending on the level of clarity and complexity, the next step may be Discovery and Assessment, a focused consultation, or preparation of a written proposal.

Discovery examines the business objective, users, workflows, systems, data, constraints, risks, priorities, and success measures. The goal is to make the recommended scope, architecture, and delivery path clearer before substantial implementation begins.

Material changes should be documented and reviewed for their effect on deliverables, schedule, responsibilities, risk, and billing. Changes are not treated as committed work until they are approved through the applicable project process.

Projects use defined milestones, review points, testing, and agreed acceptance criteria. The specific review and acceptance process is documented in the proposal, statement of work, or applicable service agreement.

Pricing depends on scope, complexity, risk, dependencies, delivery structure, and responsibilities. Custom work is described in a written proposal rather than through generic public project-price ranges.

Billing terms are documented in the applicable proposal and agreement. Custom projects may use milestone-based billing, phased billing, or another clearly written structure appropriate to the engagement.

Custom software projects are not instant-purchase products. They require discussion, scope definition, written terms, and appropriate approval before delivery begins.

Accepted payment methods will be published after an approved payment process or merchant gateway is active. Current billing terms are provided through the applicable proposal, agreement, invoice, and Payment & Billing information.

Source-code ownership, licensing, third-party components, pre-existing materials, and handoff terms are defined in the applicable agreement. The exact terms may differ depending on the engagement and are not presented as a universal promise outside the contract.

Security considerations are included in requirements, architecture, access control, validation, data handling, integrations, dependency review, testing, deployment, and maintenance as applicable to the engagement. Northbridge does not claim external audits or formal certifications that have not been completed.

Public submissions are handled according to the Privacy Policy and through the website's configured server-side and database controls. Project-specific confidentiality and information-handling responsibilities are addressed in the applicable agreement.

Yes, when ongoing support is included in a written agreement. Support may include maintenance, dependency updates, issue handling, documentation, small improvements, operational guidance, and incremental modernization.

Potentially. An assessment is normally required to understand source-code access, deployment, dependencies, documentation, data, integrations, security, known issues, and operational risk before responsibility can be accepted.

Existing clients can use the Support page, the Client Support phone number, or support@nbsoftware.net. Requests should include the relevant project or reference number where available and a clear description of the issue.