FAQs
Answers to common client questions.
If you don't see your question here, we can probably answer quickly on a call or over email. We're easy to reach.
Engagement
- Who do you work with?
- Independent small businesses, B2B vendors themselves focused on serving small businesses, and businesses that have outgrown off-the-shelf software but don't need or want an enterprise vendor. If manual work or ill-fitting tools are slowing the team down, we're probably a fit.
- What does the first engagement look like?
- We start with a free consultation. When the fit is right, we build a focused prototype so you can see the approach before we propose terms on deployment, delivery, and maintenance.
- How long does a typical project take?
- We can provide most prototypes within one week. Full builds truly depend on scope, but they usually fall between three and six weeks. We work in increments you can use as we go, not a development black box.
- Do you sign NDAs and master service agreements?
- Yes. We may need access to sensitive business information or systems in order to develop your custom solution(s). We work under standard NDAs and MSAs, and we're happy to use yours if you have a preferred template.
Pricing
- How is pricing handled?
- Every project is scoped after we understand your goals. We send a clear proposal that explains the cost to build your solution(s) and the cost to provide ongoing access support.
- Do you offer fixed price or hourly?
- Most engagements are fixed-scope and fixed-price. This typically covers the cost to build a solution and the cost to maintain and improve that solution over time. The build cost is a one-time cost, and the ongoing support is an agreed-upon monthly cost. When a project is genuinely open-ended (research, ongoing iteration, embedded help), we can work with a time-bounded retainer instead.
Build & ownership
- Do you replace our existing tools?
- We might, but it depends. Depending on what you actually need to solve for, we may integrate with what you already use and only build custom software when off-the-shelf tools force costly workarounds.
- What stack do you build on?
- It depends based on your needs, but the answer is typically: boring, durable choices that an in-house team can pick up later. We don't chase a stack because it is fashionable; we pick what fits your operation and is simple and easy to maintain.
Support
- Who do we talk to once a project is live?
- The people who built it. No support tickets, no tier-one queue, no account manager translating between you and engineering.
- What happens if something breaks?
- We respond. Critical issues are handled the same day during business hours. Non-critical changes are scoped, scheduled, and shipped on a cadence we agree on in advance.
Still wondering?
The fastest answer is usually a short call. No deck, no pitch, just a no-pressure conversation.
Let's Talk