BRICKBRIDGE

How It Works

Walk through the various steps Brick Bridge takes to develop product solutions.

A Unique Software Solution

Participate in the development and distribution of software to create a new solution for your organization.

Here's a quick overview of how it works.
Discovery & Proof of Concept

Brick Bridge partners with innovative organizations to create industry leading software products. Our co-development partners can capture their innovative or leading best organization and programmatic practices into into a cloud-based software solution.

Distribution

The solution is then made available to our partner's industry peers to utilize. This stage includes client implementations, product support, solution scaling, and the creation of brand presence. Brick Bridge has the process, expertise, and implementation strategies to make this opportunity possible.

A Deeper Dive - Three Phases, Six Stages

The process of creating and distributing successful software packages may seem like a daunting task. Brick Bridge takes pride in applying the latest lean-start and agile development processes that are proven to increase likelihood of success while controlling project costs.

PHASE 1

Discovery

The Discovery Phase is about taking the proper amount of time to research the potential of a product to create value and the level of interest in the market. Most of the work required at this Phase revolves around discussions with our co-development partner and minimal requirements needed to make a successful product for the industry.

STAGE 1

Discovery & Proof of Concept

Brick Bridge's Product Design staff will conduct interviews with co-development partner’s management to create a product requirements document. This document is intended to capture a core feature set based on the best practices of the industry. We will also explore common reporting and KPI data elements that are needed to track program delivery and impact. A Proof of Concept, or POC, is built by as an initial test development of a few critical functions found in discovery. The POC is previewed to understand if our methods will meet standards.

STAGE 2

Project Documentation

Product development estimates and quotations are reviewed both all parties at this stage. A decision to proceed with project documentation is made once the resourcing of the project is understood. The project is initial resourced by all parties via a Retainer. The Retainer guarantees delivery of project documentation that goes into detail about solution features, development costs, timelines, and responsibilities. Development begins once the project documentation and legal documents are approved and executed.

PHASE 2

Development

Brick Bridge provides employs both full custom development as well as extensive use of the cloud-based platforms. We utilize these platforms to reduce development cost for the solutions we design. We then develop smaller, custom elements to integrate with platforms to contains development costs.

STAGE 1

MVP & Alpha Development

This Phase starts with the creation of a no-frills version of the product called a Minimally Viable Product, or MVP. The MVP covers the critical data capture requirements identified in the Discovery process. A series of Iterations are then started are planned for the development more complex product layers. Feedback from the co-development partner is required at the end of each Iteration. Iterations are completed when an "Alpha Final" version is produced. This is a working version of the solution but it is not commercially complete. Our co-development partner is typically the first "user" of the product. Feedback from live use is gathered for the next stage, Beta Development.

STAGE 2

Beta Development

Additional research and live use highlight the Beta Development . First, the Alpha product is shown to industry peers for comments, demo use, and missed features. Second, feedback and improvements from the co-development partner's live use of the Alpha version are recorded and considered. All the information is compiled for a viability and cost analysis on Development-to-Market project. Only after a decision is made to invest further by all partners does development begin again. This new development follows a similar pattern as the Alpha stage with a set number of Iterations occurring based on the aforementioned information.

PHASE 3

Disribution

Strong Beta launches are key to creating early adoption among the first public users. These are users who tend to pay reduce rates for early access. These first Beta clients are selected carefully for their ability to test the product  and give feedback about how to progress key features.

STAGE 1

Market Launch

Our Partner’s industry connections are selected for a “Closed Beta”. Feedback from this group is incorporated via iterative product improvements. larger “Open-Beta” is released to the industry after Feedback from the initial Beta users is incorporated. Typically the first users in this stage are “paying” but at a discount (they will give more feedback).

STAGE 2

Product Launch

Setting a proper marketing and distribution strategy, along with a clear digital presence, are factors critical to long-term success. Our consulting services cover the strategic planning and development of these components. Lastly, we make final refinements using feedback gathered in the Beta stage to bring the product into a "Commercially Viable" state meant for wide distribution to industry peers.

1

Discovery

The Discovery Phase is about taking the proper amount of time to research the potential of a product to create value and the level of interest in the market. Most of the work required at this Phase revolves around discussions with our co-development partner and minimal requirements needed to make a successful product for the industry.

Phase 1

a

Discovery & Proof of Concept

Brick Bridge's Product Design staff will conduct interviews with co-development partner’s management to create a product requirements document. This document is intended to capture a core feature set based on the best practices of the industry. We will also explore common reporting and KPI data elements that are needed to track program delivery and impact. A Proof of Concept, or POC, is built by as an initial test development of a few critical functions found in discovery. The POC is previewed to understand if our methods will meet standards.

b

Project Documentation

Product development estimates and quotations are reviewed both all parties at this stage. A decision to proceed with project documentation is made once the resourcing of the project is understood. The project is initial resourced by all parties via a Retainer. The Retainer guarantees delivery of project documentation that goes into detail about solution features, development costs, timelines, and responsibilities. Development begins once the project documentation and legal documents are approved and executed.

Phase 2

2

Development

Brick Bridge provides employs both full custom development as well as extensive use of the cloud-based platforms. We utilize these platforms to reduce development cost for the solutions we design. We then develop smaller, custom elements to integrate with platforms to contains development costs.

a

MVP & Alpha Development

This Phase starts with the creation of a no-frills version of the product called a Minimally Viable Product, or MVP. The MVP covers the critical data capture requirements identified in the Discovery process. A series of Iterations are then started are planned for the development more complex product layers. Feedback from the co-development partner is required at the end of each Iteration. Iterations are completed when an "Alpha Final" version is produced. This is a working version of the solution but it is not commercially complete. Our co-development partner is typically the first "user" of the product. Feedback from live use is gathered for the next stage, Beta Development.

b

Beta Development

Additional research and live use highlight the Beta Development . First, the Alpha product is shown to industry peers for comments, demo use, and missed features. Second, feedback and improvements from the co-development partner's live use of the Alpha version are recorded and considered. All the information is compiled for a viability and cost analysis on Development-to-Market project. Only after a decision is made to invest further by all partners does development begin again. This new development follows a similar pattern as the Alpha stage with a set number of Iterations occurring based on the aforementioned information.

3

Distribution

Strong Beta launches are key to creating early adoption among the first public users. These are users who tend to pay reduce rates for early access. These first Beta clients are selected carefully for their ability to test the product  and give feedback about how to progress key features.

Phase 3

a

Market Implementation

Our Partner’s industry connections are selected for a “Closed Beta”. Feedback from this group is incorporated via iterative product improvements. larger “Open-Beta” is released to the industry after Feedback from the initial Beta users is incorporated. Typically the first users in this stage are “paying” but at a discount (they will give more feedback).

b

Product Launch

Setting a proper marketing and distribution strategy, along with a clear digital presence, are factors critical to long-term success. Our consulting services cover the strategic planning and development of these components. Lastly, we make final refinements using feedback gathered in the Beta stage to bring the product into a "Commercially Viable" state meant for wide distribution to industry peers.

Interested in our services?

We'd love to hear from you.

START A CONVERSATION