Skip to content
Brassnode

FAQ

Questions, answered.

Everything prospects usually ask before reaching out. Don't see yours? Send us a message.

01How long does a typical project take?

It depends on scope, but most projects fall into one of three ranges: a focused MVP or landing site takes 4–8 weeks; a full web or mobile application typically runs 3–6 months; and complex enterprise systems or platform migrations can take 6–12 months. After our discovery call, we'll give you a clear timeline estimate before any commitment.

02What industries do you work with?

We've built products across fintech, e-commerce, logistics, healthcare, education, and professional services. We don't limit ourselves to specific verticals. If there's a genuine problem to solve, we're interested. We're particularly experienced in regulated industries where security and reliability are non-negotiable.

03Do you work with early-stage startups?

Yes. Some of our best work has been with founders who had an idea and needed a technical partner to turn it into something real. We're comfortable with ambiguity and can help scope an MVP that's lean enough to validate quickly without cutting corners on the fundamentals.

04What does your tech stack look like?

On the backend, we primarily work with Laravel (PHP) and Node.js. On the frontend, we use React, Next.js, and Vue.js for web, and Flutter for cross-platform mobile. For infrastructure, we work across AWS, GCP, and DigitalOcean, with Docker and Kubernetes for containerization. We're stack-pragmatic: we'll recommend what genuinely fits your project.

05How do you handle project management and communication?

We work in two-week agile sprints with a standing demo at the end of each cycle. You'll have access to our project management tool throughout, a dedicated point of contact, and a shared communication channel. If something is at risk, you'll hear it from us before it becomes a problem.

06Do you sign NDAs?

Yes. We're happy to sign an NDA before any sensitive conversations. Client confidentiality is standard practice for us.

07Can you work with our existing codebase?

Absolutely. We regularly inherit existing codebases, sometimes well-documented, sometimes not. We'll do a technical audit early in the engagement to understand what we're working with and flag anything that needs addressing before we begin.

08What happens after launch?

We offer structured post-launch support retainers that cover monitoring, bug fixes, security updates, and incremental feature development. We can also do a clean handover to your in-house team, including documentation, knowledge transfer sessions, and a defined warranty period.

09Do you offer training for our internal team?

Yes. Our training arm runs both public programs and private corporate workshops. If you're looking to upskill your engineering team on a specific technology, workflow, or practice, we can design a custom curriculum around your needs.

10How do I get started?

Send us a message through our contact form or email [email protected] with a brief description of what you're looking to build or solve. We'll schedule a free 30-minute discovery call to understand your needs and tell you honestly whether we're the right fit.

Ready to build
something great?

Tell us what you're building or solving. We'll book a free 30-minute discovery call and tell you honestly whether we're the right fit.

Let's Talk