Question 1

What is a Proposaltype?

Accepted Answer

A Proposaltype is a proposal and a working prototype, combined. After our assessment phase, we deliver an interactive demonstration built on your actual workflows, your terminology, and your data patterns — not a PDF with assumptions. You can click through it, show it to your team, and pressure-test whether we understood the problem before committing to a full build. It's how we prove we understand your business before you spend a dollar on development.

Question 2

What is a showback?

Accepted Answer

A showback is our weekly progress demonstration. Every week during the build phase, we show you what we built — not a status update or a slide deck, but the actual working solution. You click through it, test it, and tell us what needs to change. It's how we make sure you never go more than five business days without seeing real progress.

Question 3

How long does a typical engagement take?

Accepted Answer

Most first engagements run 10–14 weeks from assessment through launch. The Assessment and Proposaltype phase takes 1–2 weeks, strategy takes another 1–2 weeks, and the build phase typically runs 8–12 weeks. The exact timeline depends on the scope and complexity of what we're building.

Question 4

Do I have to commit to the full build upfront?

Accepted Answer

No. The Assessment and Proposaltype phase is a standalone engagement. You evaluate the Proposaltype with your team and decide whether to move forward. There's no commitment to the full build until you've seen proof that we understand the problem.

Question 5

How involved do I need to be during the project?

Accepted Answer

We ask for about an hour per week — attending the weekly showback and giving us feedback. During the Assessment phase, we'll need more of your team's time (interviews, workflow observations), and during Strategy sign-off, you'll want to review the documentation closely. But during the build, one hour a week keeps the project on track.

Question 6

What happens if I don't like what I see in a showback?

Accepted Answer

That's exactly what showbacks are for. You tell us what's wrong, and we adjust the following week. Because we show you progress every week, problems get caught early — not after months of development. Your feedback directly shapes what we build next.

Question 7

How big is your team?

Accepted Answer

We're a senior-led engineering practice. A typical engagement is staffed with 2–3 engineers, every one of them at a senior level. You won't be handed off to junior developers learning on your project.

Question 8

Do you work on-site or remotely?

Accepted Answer

Both. During the assessment phase, we come to you — we need to see how your team actually works. During the build phase, we work remotely with weekly showbacks and regular communication. We're based in Cincinnati, so on-site visits for Midwest clients are easy to arrange when needed.

Question 9

What industries do you specialize in?

Accepted Answer

We build solutions for eight industries: IoT & Connected Systems, Manufacturing, Healthcare, Financial Services, Construction, Field Services, Law, and GovTech/B2G. Our team has led engineering operations inside companies in each of these verticals — we don't just study your industry, we've worked in it.

Question 10

Do you work with startups?

Accepted Answer

We work best with mid-market operational companies — typically 200 to 5,000 employees — where the problem is coordination across systems and teams. We're not the right fit for early-stage startups still finding product-market fit, but we're a great fit for established companies whose operations have outgrown their tools.

Question 11

Where are you located?

Accepted Answer

Cincinnati, Ohio. We serve clients nationally, but we have deep roots in the Cincinnati business community — one of the country's densest hubs for mid-market operational companies in healthcare, manufacturing, law, and financial services.

Question 12

Who owns the code when the project is done?

Accepted Answer

You do. 100%. You own the code, the infrastructure, the deployment pipeline, and all documentation. There's no licensing, no lock-in, no recurring fees for the software itself. If you want to hand the system to an internal team or another firm, you can do that the day we finish.

Question 13

What do I actually get at the end of an engagement?

Accepted Answer

You get a working, deployed solution, plus: full source code, deployment documentation, infrastructure configuration, and training for your team. Everything you need to operate and maintain the system independently.

Question 14

Can I bring my own developers into the project?

Accepted Answer

Yes. We're happy to work alongside your internal team. In fact, we often do — it helps with knowledge transfer and makes the handoff smoother. We can also help mentor junior developers on your team during the engagement.

Question 15

What if I need changes after launch?

Accepted Answer

We offer optional ongoing maintenance agreements for monitoring, bug fixes, and feature iterations. But you're never locked in — you own the code, so you can also make changes with your own team or another firm. We build systems that can live without us.

Question 16

How do you charge?

Accepted Answer

We scope to fixed outcomes, not hourly billing. You'll know the cost before we start. We don't pad timelines to maximize billing — if we can solve your problem in 6 weeks, we do. Our model incentivizes speed and quality, not hours logged.

Question 17

How much does a typical project cost?

Accepted Answer

It varies by scope and complexity, but a typical first engagement with a 2–3 person senior team over 10–14 weeks represents a significant investment. The Assessment and Proposaltype phase is a smaller standalone engagement that lets you evaluate our work before committing to the full build. We're happy to discuss specifics on a call.

Question 18

Do you offer ongoing support contracts?

Accepted Answer

Yes. After launch, we offer maintenance agreements that cover infrastructure monitoring, bug fixes, and feature iterations. These are optional — you're never required to keep us on retainer. The system is yours.

Question 19

What's in the Assessment and Proposaltype engagement?

Accepted Answer

You get a 1–2 week assessment where we learn your operation — interviews, workflow observation, systems review — followed by delivery of your Proposaltype: an interactive, clickable prototype built on your actual workflows. You also get a prioritized problem list. This is a standalone engagement with its own scope and price, and there's no obligation to proceed to the full build.

Question 20

What technologies do you use?

Accepted Answer

We choose the right tools for the problem, not the other way around. We work across modern web frameworks, cloud infrastructure (AWS, Azure, GCP), mobile platforms, and integration middleware. The specific stack depends on your existing systems, your team's capabilities, and the requirements of the project. We'll recommend an approach during the strategy phase and explain why.

Question 21

Can you integrate with our existing systems?

Accepted Answer

That's what we do best. Most of our work involves connecting systems that don't talk to each other — ERP to shop floor, billing to operations, field tools to back office. We have deep experience with legacy system integration, API development, and building the connective tissue between tools your teams already use.

Question 22

Do you build mobile apps?

Accepted Answer

Yes, when mobile is the right solution for the problem. Many of our projects include mobile components — especially for field services, fleet management, and construction where teams need to work from a phone or tablet. We build for both iOS and Android.

Question 23

Will the solution scale as we grow?

Accepted Answer

Yes. We architect for your current needs with a clear path to scale. We've built platforms that serve millions of subscribers, manage hundreds of thousands of connected devices, and handle the compliance requirements of publicly regulated industries. We'll talk through your growth trajectory during the strategy phase and build accordingly.

Frequently asked questions.

Our Process

Working With Us

Ownership & Deliverables

Pricing & Contracts

Technology

Tell us about your project.