Frequently asked questions

We focus on operations-led businesses in logistics, field services, finance operations, manufacturing, and membership organizations. Typically companies with 50-500+ employees, complex workflows, and annual revenues of $5M to $500M+. If you're unsure if we're a fit, let's talk about it.

Good fit signals: Your team outgrew spreadsheets or off-the-shelf software. You have complex workflows that generic tools don't serve. You want software designed specifically for how you operate. You're willing to be involved in discovery and design, not just hand it off. If these resonate, we should talk.

We start with interviews and observation. We'll spend time with your team, understand the workflows, map pain points, and identify the specific problems we're solving. We'll create a strategy document, propose solutions, and get alignment before we start building. This typically takes 2-4 weeks depending on complexity.

It depends on scope. A Focus Sprint might be 2-4 weeks. A full product build (Product Partnership) is typically 3-6 months. Embedded Delivery is ongoing. We'll give you a realistic timeline after discovery, but we stay flexible as you learn more about what actually needs to happen.

Project-specific. We don't have fixed rates because each project is different. A small tool might be $50K-$100K. A complete application could be $200K-$500K or more. After initial conversations and discovery, we'll propose budget and timeline that work for your situation.

Yes. Most of our work involves connecting to legacy systems, existing databases, APIs, and third-party tools. We often build integration layers that translate between disparate systems. That's actually one of our specialties—making fragmented systems work together coherently.

Absolutely. If you have existing infrastructure, preferred languages, or technology constraints, we work with them. We'll recommend tech choices, but we're pragmatic about using what you already have if it makes sense. We're language-agnostic.

You own it. Full intellectual property, full source code, full rights to modify, maintain, or hand off to another team. We transfer ownership and documentation at the end. You're never locked in.

It depends on the engagement model. With Embedded Delivery, we stay on as part of your team, continuously improving and adding features. With Project Partnerships, we can transition to a support/iteration phase if you want. You don't have to choose forever—we can revisit the arrangement as your needs change.

Accessibility is built in from day one, not bolted on later. We audit for WCAG AA compliance and test with real assistive technology. For security: encryption in transit and at rest, secure authentication, regular audits, and compliance with relevant standards for your industry. We take this seriously.

Either. We can be your complete development partner, or we can embed within your existing team. If you have engineers, we work alongside them. If you don't, we build it. The approach depends on what you need and your team's capacity.

We define scope clearly upfront. Changes get discussed and priced separately—we don't just absorb them. We're collaborative about this. Sometimes what seemed like a small change is actually complex, and we'll explain why. Sometimes we find a better way that's worth reconsidering the scope. It's a partnership conversation.

Yes. With Embedded Delivery, it's continuous. With other engagement models, we can set up ongoing support separately—bug fixes, performance improvements, infrastructure maintenance, feature additions. We have support levels (Critical, High, Normal) with different response times.

Heavy involvement from your team. We prototype risky parts early. We test assumptions. We iterate based on actual usage, not guesses. We stay in constant communication. We ask hard questions when something doesn't feel right. This is how we avoid building something technically perfect but operationally useless.

Honest conversations early. If direction is wrong, we adjust. If pace isn't working, we talk about it. We'd rather reset expectations or pause than keep moving in the wrong direction. It's happened before and we handle it professionally.