Frequently Asked Questions
Last updated on April 7, 2026
What technologies do you specialize in?
We work across the full stack — React, Next.js, Node.js, Python, and cloud infrastructure on AWS and GCP. We choose what fits the problem, not what’s most familiar to us.
Do you work with legacy systems?
Yes — and we know how painful they can be. We assess first, propose a migration path second, and make sure nothing breaks in the process.
Can you help us figure out which technology is right for us?
That’s often where we start. A 30-minute call is usually enough to give you a real recommendation — not a vendor pitch.
Do you work with startups or only established companies?
Both. We’ve taken founders from idea to MVP and helped established companies untangle years of technical debt.
Where is your team located?
We’re based in Kyiv, Ukraine, with experience working across European and US time zones.
How long has Genius Software been operating?
We’ve been building software products since 2015 — long enough to have made the mistakes so you don’t have to.
What industries have you worked in?
Fintech, healthcare, e-commerce, logistics, education, and SaaS. The domain changes; the engineering discipline doesn’t.
Can I see examples of your previous work?
Yes. We have a portfolio on our website, and for specific niches we can share relevant case studies under NDA if needed.
Do you build mobile apps as well as web?
Yes — React Native for cross-platform mobile, and we’ll recommend native development when performance demands it.
Do you do design as well as development?
Yes. We have UI/UX designers on the team who work closely with developers from the start, not as an afterthought.
Can you take over a project that another agency started?
We can. We’ll do a code audit first so everyone understands what we’re inheriting, then give you an honest assessment before committing.
Do you work on open source projects?
Some of our team contributes to open source, and we’re happy to build on open source foundations when it makes sense for your project.
Are you a product company or a services company?
Services. We build for you, not for ourselves. Our focus is on your outcomes, not on pushing our own tools or platforms.
How big is your team?
We’re a focused team of around 40 people — large enough to staff projects properly, small enough that you’ll never feel like a ticket number.
Do you take on projects outside Ukraine?
Yes. Most of our clients are international — primarily from the US, UK, Germany, and the Netherlands.
What makes you different from other software agencies?
Honesty, mostly. We don’t oversell, we don’t disappear after launch, and we don’t tell you what you want to hear if it’s not true.
Do you offer consulting without full development engagement?
Yes. If you need a technical audit, architecture review, or second opinion, we can scope that as a standalone engagement.
Can you work with our existing vendor or partner?
Usually yes. We’ve collaborated alongside other agencies, freelancers, and in-house teams on shared projects without issue.
What happens if we're not happy with the work?
We address it directly. If something isn’t right, we fix it. Our goal is a relationship that lasts beyond a single project.
How do we get started?
Book a 30-minute call. No forms to fill, no sales deck — just a conversation about what you need.
How do you structure a typical project?
Short delivery cycles of one to two weeks. You see real progress regularly, give feedback early, and nothing gets built in a vacuum for months.
Do you follow Agile or Scrum?
We use Agile principles without forcing rigid ceremony. Standups, sprint reviews, and planning happen when they add value — not just because it’s on the calendar.
How do you handle requirements that aren't fully defined yet?
We run a discovery phase to shape requirements before writing code. Starting with clarity saves everyone time and money.
Will I be involved during development or just at the start and end?
Throughout. We share progress regularly and make it easy to give feedback at every stage.
How do you approach code quality?
Code reviews on every pull request, automated testing, linting, and clear standards documented from day one. Quality isn’t a phase — it’s built into the process.
Do you write tests?
Yes. Unit tests, integration tests, and end-to-end tests depending on what the project needs. We don’t ship untested code to production.
How do you manage version control?
Git, always. With a branching strategy agreed at the start of the project so there are no surprises when things need to merge.
What project management tools do you use?
Typically Jira or Linear for task tracking, Confluence or Notion for documentation, and Slack for communication. We can adapt to tools you already use.
How do you handle bugs found during development?
They go into the backlog immediately, get prioritized by severity, and are fixed within the same sprint when critical.
Do you do code reviews?
Every pull request is reviewed by at least one senior developer before it’s merged. No exceptions.
How do you approach performance optimization?
We build with performance in mind from the start — not as a last-minute fix before launch. Profiling and load testing are part of our standard process.
Do you use CI/CD pipelines?
Yes. Automated build, test, and deployment pipelines are standard on every project. Manual deployments are a thing of the past.
How do you handle technical debt?
We flag it as it accumulates and recommend addressing it before it compounds. We won’t ignore it just to ship faster.
What happens during a sprint review?
You see what was built, give feedback, and we adjust priorities for the next sprint. It’s a real conversation, not a presentation.
Do you do pair programming?
For complex problems or onboarding new team members, yes. It’s one of the most effective ways to transfer knowledge and catch issues early.
How do you approach accessibility?
WCAG 2.1 AA compliance is our baseline for web projects. If your audience requires a higher standard, we build to that.
Do you use design systems?
Yes. We either adopt an existing one or help you build one, depending on the project scale. Consistency across a product matters.
How do you handle API integrations with third-party services?
We document every integration, write proper error handling, and test against real and mock endpoints. Third-party APIs break — we build for that.
What's your approach to database design?
Schema design gets proper attention before any code is written. Changing a data model later is expensive; getting it right early is not.
How do you manage dependencies and keep them up to date?
We track dependencies actively, update regularly, and address security vulnerabilities as soon as they’re reported upstream.
How do you price your work?
Either fixed-price for well-defined scope, or time-and-materials for evolving work. We’ll recommend the model that fits your situation.
Do you require a large upfront payment?
No. Payments are tied to milestones or monthly cycles — you pay for work done, not work promised.
Can we start small and scale up?
Yes. Many clients begin with a discovery phase or small scoped project before committing to something larger. We prefer it that way.
What's the minimum engagement size?
We’re most effective on projects with at least four to six weeks of scope. Shorter than that doesn’t give us enough time to do the work properly.
Do you offer retainer engagements?
Yes. For ongoing development or support, a monthly retainer gives you guaranteed capacity and faster response times.
How do you handle scope changes that affect cost?
Any change that affects cost gets flagged and agreed before we act on it. No surprise invoices.
Do you charge for discovery and planning?
For larger projects, yes — discovery is real work that has real value. For smaller engagements we often fold it into the project estimate.
What currencies do you invoice in?
USD and EUR primarily. We can accommodate other currencies depending on the client’s location.
Do you offer discounts for long-term engagements?
For multi-month or ongoing engagements, yes. We value stable relationships and we price to reflect that.
Can we pause a project and resume later?
In some cases yes, depending on team availability. We’ll be upfront about whether a gap affects continuity or cost.
What payment methods do you accept?
Bank transfer is standard. We can discuss alternatives for clients where that’s not straightforward.
Do you offer equity arrangements for startups?
In rare cases and for the right project, yes. It requires a deeper conversation and isn’t our default model.
How are change requests handled in a fixed-price project?
Small changes are absorbed where reasonable. Significant scope additions are quoted separately and approved before work begins.
Is there a setup or onboarding fee?
No. Onboarding is part of the project cost — we don’t charge extra for getting started.
How do you estimate project cost?
We break the work into components, estimate each one, add a realistic buffer, and explain every line. No magic numbers.
What happens if the project goes over budget?
On fixed-price projects, that’s our risk to manage. On time-and-materials, we flag it early so you can decide how to respond.
Can we reduce scope to fit a budget?
Always. We’d rather help you ship something smaller and valuable than overpromise and under-deliver.
Do you provide detailed invoices?
Yes. Every invoice shows what was worked on, by whom, and for how long where applicable. No black-box billing.
What's your typical payment schedule?
Milestone-based for fixed projects, monthly for retainers and time-and-materials work.
Can we get a rough estimate before a formal proposal?
Yes. After a short discovery call we can usually give you a ballpark range — enough to know if it’s worth going deeper.
Who will actually be working on my project?
A dedicated team — typically a lead developer, supporting engineers, and a project contact. You’ll meet them before work begins.
Will the team change mid-project?
We do everything we can to keep the team stable. If something changes, we transition carefully and ensure no loss of context.
What does day-to-day communication look like?
A shared Slack workspace, regular async updates, and a standing check-in as needed. You’re never left wondering what’s happening.
Do you work with our in-house team or separately?
Either. We can embed alongside your developers or work as a standalone team with defined handoffs.
What time zones do you cover?
We’re based in Kyiv (EET/EEST) and have worked comfortably with clients in US Eastern, Central European, and UK time zones.
How do you onboard onto a new project?
We spend the first few days understanding your codebase, your goals, and your team before writing anything. Rushing this costs time later.
Who is our main point of contact?
A dedicated project lead who knows your work inside-out and is reachable during business hours without going through a ticketing system.
Do you involve the client in hiring decisions for their project team?
For longer engagements, yes. We’ll introduce the proposed team and make sure you’re comfortable before we start.
How do you handle disagreements about approach or direction?
We raise them honestly and early. If we think a decision is wrong, we’ll say so — with reasoning. Ultimately the client decides.
Can we meet the team before signing?
Yes. We encourage it. A short intro call with the people who’ll actually do the work is a reasonable ask.
Do you use contractors or only full-time employees?
Primarily full-time employees. When we bring in specialists for specific needs, they’re vetted and work under the same standards.
How do you handle knowledge transfer if the project ends?
Structured and documented. We don’t just hand over files — we walk your team through the codebase and answer questions until they’re comfortable.
Can we communicate directly with developers or only through a PM?
Both. We encourage direct technical communication while keeping the project lead in the loop for anything that affects scope or timeline.
How do you handle cultural or language differences?
Our team works in English daily. We’re direct, professional, and experienced enough to communicate clearly across cultures.
What collaboration tools do you use?
Slack, Jira or Linear, Figma, Notion or Confluence, and GitHub or GitLab. We adapt to your existing stack where it makes sense.
How do you keep the client informed without overwhelming them?
A weekly written update covering what was done, what’s next, and anything that needs a decision. Short and scannable.
Do you do retrospectives?
Yes, at the end of each sprint and at project milestones. They’re genuinely useful — not just a checkbox.
What happens if a team member goes on leave during the project?
We plan for it. Leave is scheduled in advance and covered without impacting your timeline.
Can we expand the team quickly if the project needs it?
Within reason, yes. We keep a bench of available talent for situations where scope grows faster than expected.
How do you handle feedback that conflicts between stakeholders on the client side?
We flag the conflict clearly and ask you to align internally before we proceed. Building to conflicting requirements is how projects go wrong.
How long does a typical project take?
A focused MVP usually takes eight to fourteen weeks. We give realistic estimates — not numbers designed to win the deal.
What happens if a deadline is at risk?
We flag it early, not the day before. You’ll hear about it with enough notice to make real decisions.
Can you work to a fixed deadline?
Yes. When the deadline is non-negotiable, we scope the work to fit it — which means an honest conversation about what’s in and what’s out.
Do you deliver documentation alongside the code?
Yes. Technical documentation is standard, so your team — or a future team — can understand and maintain what we built.
How do you define "done"?
Code reviewed, tested, deployed to staging, accepted by the client, and documented. Not just “it works on my machine.”
What does a typical launch look like?
A staged rollout — staging environment first, then production with monitoring in place. We don’t flip switches and hope.
Do you do user acceptance testing before launch?
Yes. We build it into the timeline and support you through it, not just hand things over and step back.
How do you handle last-minute changes before launch?
We assess the risk honestly. Some changes are fine; others can destabilize a launch. We’ll tell you which is which.
Can you deploy to our existing infrastructure?
Usually yes. We’ll review your setup early so there are no surprises on launch day.
How do you handle post-launch monitoring?
Error tracking, uptime monitoring, and performance dashboards are set up before go-live, not after something breaks.
What's your process for hotfixes after launch?
Critical issues get same-day response. We assess, fix, test, and deploy — in that order, even under pressure.
Do you provide release notes?
Yes. Every deployment includes a clear summary of what changed, what was fixed, and anything the client needs to know.
Can we do a soft launch to a limited audience first?
Yes, and we often recommend it. Real user feedback before a full launch saves a lot of pain.
How do you handle time zone differences around launch day?
We coordinate schedules in advance to make sure the right people are available when it matters.
What's included in the handover at the end of a project?
Source code, documentation, credentials, deployment guides, and a walkthrough session with your team.
Do you stay available after handover for questions?
Yes. There’s always a period after handover where questions come up. We don’t disappear the moment the invoice is paid.
How do you estimate timelines for projects with unclear scope?
We break what we know into phases and estimate the first phase concretely. Future phases are estimated as the scope becomes clearer.
What's the longest project you've delivered?
Multi-year platform builds for clients who kept extending the engagement. Long projects are a sign the relationship is working.
Do you work weekends or holidays for critical launches?
When it’s genuinely necessary, yes. We plan to avoid it, but we don’t abandon clients at critical moments.
How do you measure project success?
Against the goals defined at the start — not just whether the code shipped, but whether it did what it was supposed to do.
How do you handle data security during development?
Encrypted connections, access controls, no production data in development environments, and secure credential handling throughout.
Do you sign NDAs?
Always, before any sensitive information is shared.
Can you help us meet GDPR requirements?
Yes. We’ve built GDPR-compliant systems and can help you design for compliance from the start rather than retrofitting it later.
Who owns the code once the project is delivered?
You do. Full IP transfer is standard in every engagement.
Do you follow OWASP security guidelines?
Yes. The OWASP Top 10 is our baseline for web application security. We go further when the project requires it.
How do you handle authentication and authorization?
Proper role-based access control, secure session management, and modern authentication standards (OAuth 2.0, JWT) depending on what the project needs.
Do you conduct security testing?
Yes — penetration testing and vulnerability scanning are available as part of our delivery process or as standalone engagements.
How do you store sensitive data like passwords?
We never store plain-text passwords. Bcrypt or Argon2 hashing is standard. Sensitive data at rest is encrypted.
Can you help with HIPAA compliance for healthcare projects?
Yes. We understand the requirements and can architect systems that meet them — audit logging, access controls, data encryption, and more.
How do you manage access to client systems and credentials?
Through a password manager with role-based access. Credentials are never shared over email or chat, and access is revoked at project end.
Do you perform dependency vulnerability scanning?
Yes. Automated tools flag vulnerable dependencies and we address them promptly — especially critical CVEs.
How do you handle security incidents during a project?
We notify you immediately, contain the issue, investigate the cause, and document the resolution. No covering things up.
Do you use environment variables for secrets?
Always. Secrets never go into source code or version control. Environment configuration is managed separately and securely.
Can you help us build a security policy or documentation?
Yes. For clients who need it, we can produce security documentation, data flow diagrams, and policies as part of the engagement.
How do you approach secure API design?
Rate limiting, input validation, proper authentication, HTTPS only, and meaningful error messages that don’t leak system information.
Do you have experience with SOC 2 compliant systems?
Yes. We’ve built systems for clients operating under SOC 2 requirements and understand what that means for architecture and process.
How do you handle user data across different regions?
We design for data residency requirements from the start — where data is stored, processed, and transferred matters and we treat it accordingly.
What happens to our data and access after the project ends?
All access is revoked, credentials are rotated, and any client data held during development is deleted. We document the cleanup.
Do you do code audits for security?
Yes, as a standalone service or as part of a project. A fresh set of eyes on existing code often finds things that have been missed.
How do you keep up with evolving security threats?
Through regular training, security community resources, and a culture of treating security as an ongoing responsibility — not a one-time checklist.
What technologies do you actually specialize in?
We work across the full stack — React, Next.js, Node.js, Python, and cloud infrastructure (AWS, GCP). But honestly, the tech is secondary. We pick what fits your problem, not what we happen to know best. If something isn’t a fit, we’ll tell you upfront.
Do you work with legacy systems?
Yes — and we know how painful they can be. We’ve helped companies modernize codebases that nobody wanted to touch. We always assess first, propose a migration path second, and make sure nothing breaks in the process. No big-bang rewrites unless absolutely necessary.
Can you help us figure out which technology is right for us?
That’s often where we start. A 30-minute call is usually enough to map your situation and give you a real recommendation — not a vendor pitch. We’re vendor-agnostic, so the answer is whatever actually makes sense for your team and your scale.
Do you offer ongoing support after launch?
Yes. We offer retainer-based support for teams who want ongoing help, and one-off maintenance packages for specific fixes. We don’t disappear after handoff — some of our longest client relationships started the day a project “ended.”
How do you handle projects that change scope midway?
Scope changes happen — we don’t penalize you for them. We work in short delivery cycles so you see real progress every 1–2 weeks. If priorities shift, we adjust. Any change that affects cost or timeline gets flagged clearly before we move forward, not after.
What does working with you actually look like day-to-day?
You’ll have a single point of contact who knows your project inside-out. Expect regular async updates, a shared task board, and a standing check-in as needed. No status-report theater — just clear communication and work that actually ships.
