Frequently asked questions
Everything you need to know about working with us. Can't find what you're looking for? Get in touch.
These are the questions buyers ask us most: what we charge, how the first-sprint guarantee works, where our engineers are, how we handle GDPR and who owns the code. If yours isn't here, ask us on a call.
How does the first-sprint guarantee work? +
Before the first sprint we agree written acceptance criteria: what the two-week sprint must deliver and how we'll check it. At the sprint-1 demo we go through them together. If they aren't met, you can stop the project and you don't pay for that sprint. It lets you judge our engineers, communication and code quality on real work, not a pitch.
What do you charge? +
Our prices are published. An AI Production Audit is €3,500 and an AI Production Launch €20,000–35,000 depending on scope. A code audit is €1,900, or €3,500 for large codebases. Delivery Pods cost €4,200 (Care Lite), €8,200, €14,000 or €23,000 a month. E-commerce packages start at €6,000. Team extension starts at €45/hour for mid-level and €60/hour for senior engineers. Custom projects typically land between €30,000 and €150,000 and get a fixed price after discovery. All prices exclude VAT.
How do payments work? +
The AI Production Launch is paid 30% at signing, 40% at the mid-point demo and 30% at production acceptance. Delivery Pods are prepaid monthly. Other fixed-price projects are paid against milestones written into the proposal. We invoice from Smoother Development AB, Sweden.
Where are your engineers? +
Our engineering team works from Ukraine. The company, the contract and the accountability are Swedish: you sign with Smoother Development AB, and a founder is accountable for every project.
How do you handle GDPR when engineers are outside the EU? +
Ukraine has no EU adequacy decision, so any access to personal data from Ukraine is covered by the EU Standard Contractual Clauses (GDPR Art. 46) in our data processing agreement. Where possible we keep personal data in EU-region systems in your cloud account and give engineers least-privilege access, often without any access to production personal data.
What happens if an engineer becomes unavailable? +
Every project has a second engineer who knows the codebase, code is pushed to a repository you can access at all times, and infrastructure is defined as code. Our team has worked through power and connectivity disruption since 2022 with backup power and connections, and we plan delivery so a short outage doesn't move a milestone.
Who owns the code? +
You do, once the related invoice is paid. That's written into the contract. When an engagement ends you get the repositories, infrastructure code, credentials and documentation.
Can we talk to a past client? +
Yes. After the first call we can put you in touch with a client from a similar project, if they agree. Many of our projects are under NDA, so we'll describe those in detail on a call instead.
What technologies do you specialize in? +
Our core technology stack includes React, Vue.js, Next.js, and Nuxt.js for frontend development; Node.js, Go, and TypeScript for backend services; PostgreSQL, Redis, and Elasticsearch for data storage; AWS and Google Cloud Platform for infrastructure; and Docker, Kubernetes, and Terraform for DevOps. For AI projects, we work with OpenAI, Anthropic Claude, Google Gemini, LangChain, Vercel AI SDK, and vector databases like Pinecone and pgvector. That said, we're stack-agnostic — we choose the best tools for each specific project rather than forcing a one-size-fits-all approach.
How do you handle project communication? +
You'll communicate directly with the engineers building your product — not through account managers or project coordinators. We typically use Slack or Teams for daily communication, hold weekly status calls with screen-sharing demos of completed work, and share progress through your preferred project management tool (Jira, Linear, Asana, etc.). Every sprint ends with a demo where you see working software and provide feedback that directly shapes the next sprint's priorities.
Do you work with startups or only larger companies? +
We work with both growth-stage startups and established businesses. For startups, we typically help build MVPs and scale initial products, often working closely with founders who have a technical vision but need experienced engineering capacity. For larger companies, we usually handle specific projects like modernizing legacy systems, building new microservices, or integrating AI capabilities. Our flexible engagement models — fixed price, time & materials, and dedicated team — allow us to adapt to different company sizes and needs.
How quickly can you start a new project? +
Typically within 1–2 weeks of signing. For team extension we can often add developers within a few days. We always begin with a short discovery phase to understand your requirements and set up the development environment, followed immediately by the first sprint.
Do you provide design services as well? +
Yes, as part of a project. Our core expertise is software engineering, and we include UX/UI design support for wireframes, user flows and interface design where a project needs it. If you already have designs from your own team or another agency, we implement them.
How do you ensure code quality? +
We use several layers of quality assurance. All code goes through peer review before merging. We write automated tests (unit, integration and end-to-end) as part of every sprint, focused on critical paths. CI/CD pipelines run linting, type checking and tests on every commit, and every project includes documentation so the codebase stays maintainable.
Can you take over an existing codebase? +
Absolutely. Many of our engagements involve inheriting and improving existing codebases. We start with a thorough code audit to understand the current state of the system — architecture, code quality, test coverage, security vulnerabilities, and technical debt. Based on this audit, we create a prioritized improvement plan and discuss it with you before making any changes. We've successfully taken over projects built by other agencies, in-house teams, and freelancers, stabilizing and improving them while adding new features.
Can you take over an app built with Lovable, Bolt or Cursor? +
Yes. Our Vibe-Code Rescue starts with a fixed-price code and security audit (€1,900 for a typical app, 3–5 business days; €3,500 for large codebases) and continues with a fixed-price stabilization, usually without rebuilding the app.
What industries do you have experience in? +
We've delivered projects in construction, e-commerce, SaaS, recruitment, cybersecurity and the public sector; our case studies show examples. Our deepest experience is in business platforms, marketplaces and AI-powered tools, and we pay attention to the regulations that come with each domain, such as GDPR and NIS2.
Still have questions?
Ask a founder directly. No sales pitch, just straight answers about what we can build together.
Book a 30-minute callLet's talk about what you want to build
Tell us briefly what you want to build, fix or put into production. You'll talk to a founder, not a salesperson.
Book a 30-minute call
Pick a time in Daniel's calendar. You'll get an invite with a video link, and we'll come prepared with questions about your goal.
Pick a time- 1 A founder reads your message and usually replies within one business day.
- 2 We agree a time for a 30-minute call to understand your goal, systems and constraints.
- 3 You get a written next step: a fixed-price proposal, a paid audit, or an honest "we're not the right fit".
Prefer e-mail? [email protected]
Or send us a message