Test it on a live program.
Good ideas die in demos. Most programs learn they are late months after the data said so. We give promising forecasting models, analytics and data tools a fair trial with our analysts, on live controls work, measured against how we forecast today.
Ideas that earn their place.
- I1
A real problem, stated plainly
Late warning on slip, unreliable EACs, hours lost to manual reporting, change orders priced too slowly. Tell us which problem you solve and how you know it matters.
- I2
Something analysts will use
If it adds hours to the monthly update cycle, it will not survive. We look for tools that fit how schedulers and cost engineers actually work.
- I3
A way to measure it
Forecast error, weeks of earlier warning, hours saved per report. Pilots need a baseline and a number to beat.
- I4
Explainable output
An owner will ask why the model says the P80 date moved. Predictions need reasons a controls lead can defend in a board meeting.
- I5
A path to scale
If the pilot works, we want to roll it out across engagements. Tell us what that takes in data, training, support and cost.
How a pilot works.
A short, honest process. If an idea is not right for us, we will tell you why so you can take it somewhere it fits.
Use the form below. Describe the problem, the solution and any results you already have.
Our scheduling, cost, risk or reporting leads review it, depending on what it touches, and set up a call if it looks promising.
We agree the data, the duration and the measures of success in writing, along with who pays for what and how client data is protected.
Our analysts run it alongside our standard methods on redacted or approved program data. You get honest feedback, not a polished survey.
We share the results and decide on next steps: refine and retest, roll out to more engagements, or part ways with lessons learned.
What innovators can expect.
The same commitments on every engagement, in every market, whatever the size of your firm.
- Terms
- Clear terms, agreed up frontPilot terms, including any fees, licenses and who covers them, are agreed in writing before the pilot starts.
- Standards
- One method on every programEvery pilot goes through a data security and confidentiality review before it touches client data.
- Communication
- Straight answers, earlyDirect access to the analysts running the pilot, and a written summary of results at the end.
- Growth
- Mentoring for emerging firmsEarly-stage and emerging firms can tap the same mentoring we offer controls professionals through Rising Controls Professionals.
Submit an idea.
Tell us the problem, your solution and where it stands today. Keep confidential details out of this first message. We can discuss them under a nondisclosure agreement later.
Prefer to talk first? Email the partnership team.
partnership@konradbeck.comInnovation questions.
Do you pay for pilots?
It depends on the pilot. Costs, licenses and any fees are agreed in writing before anything touches program data, so both sides know the terms.
What happens to my intellectual property?
It stays yours. Keep confidential details out of your first submission. If we move forward, we can sign a nondisclosure agreement before going deeper.
How do you handle client data in a pilot?
Client data is never shared without permission. Pilots run on redacted data or data the client has approved for that use, under written terms.
Can an associate or technology partner submit an idea?
Absolutely. Some of the best improvements come from the people already doing controls work. Licensing questions go to techlicense@konradbeck.com.
How do I follow up on a submission?
Email partnership@konradbeck.com with the name of your idea and we will tell you where it stands.
Show us an earlier warning.
Send your idea or email the partnership team. If it can show a slipping program sooner, we want to try it.