From First Call to Working Prototype
We will share a working prototype for you to try before committing to a plan.
The process
Tell us what is slowing you down.
A short form, three minutes.
A 15-minute conversation.
We confirm the shape of the problem, who else belongs in the room, and whether this is a fit for both sides.
A 45-minute engineering call.
Our developers get into specifics: your systems, your data, your process, and what a build would realistically involve.
A one-week prototype, at no cost.
We design three to five screens with sample data so you can click through the concept.
A working session to review it.
We walk it together, refine the scope, and decide whether to move forward.
The prototype is a visual model built to test the concept, using sample data. It remains the property of Upstream Impact until an engagement begins.
What the Prototype Week Looks Like
A sample project. Three screens, built on sample data over five days, then reviewed with your team.
Illustration with sample data. A prototype of a jobs screen takes shape over five days: a wireframe on day one, the layout on day two, sample data on day three, two more screens on day four, and a reviewed set of screens on day five. The point is that you see working screens built on your own kind of data in the first week, not a document describing them.
Scope, Time, and Investment
90–180 days
Most engagements run 90 to 180 days from kickoff.
$10,000–$75,000
Driven by how many systems have to connect, how much existing data comes across, and how many people will use the finished application.
We quote annual maintenance before you commit rather than after.
Why Teams Choose a Custom Build
We build the system around your process, rather than reshaping your process to fit someone else's software. Where an existing application still works, we extend it, which protects the data and the institutional knowledge inside it. Keeping your ERP close to standard also protects you at upgrade time, since a purpose-built application alongside it can read from the ERP through its API. And because the application is yours, everyone who needs it has it, on any device, working from the same current information.
Questions About Cost, Timeline, and Working Together
How much does custom software cost for a mid-size manufacturer?
Our projects run $10,000 to $75,000. Cost tracks three things: how many systems have to connect, how much existing data comes across, and how many people use the finished application. Work above roughly $90,000 usually belongs with a larger firm, and we will say so early.
How long does a custom software build take?
Typically 90 to 180 days from kickoff. Longer timelines mean more integrations or more complicated data, rarely more screens.
What is the free prototype, exactly?
After the engineering call, we spend a week designing three to five screens with sample data so you can click through the concept before spending anything. It is a visual model rather than a working application.
Do we need an RFP for a project this size?
Usually not. At this scale a conversation and a prototype tell you more than a document exchange will. Projects above roughly $90,000 are where an RFP and a larger vendor start to make sense.
Let’s chat.
Fifteen minutes is enough to tell whether there is a build worth scoping. Bring the process that frustrates you most, and we will tell you honestly whether custom software is the right answer.
Does earlier in the week or later work better for a 15-minute call?