Frequently Asked Questions
What clients usually ask before we start: how we work together, how we price, how we communicate and how we protect your code and data.
About Smartym Pro
We are a software engineering company working with start-ups, scale-ups and enterprises. We take on four types of work: custom software development for a defined system or module, team extension when your team needs more engineers, MVP and product development for a new product, and application modernisation for systems already in production. For a long-term business goal we also run a dedicated development team.
Our main areas of expertise are enterprise Java and Oracle, web front ends, mobile apps and applied AI and automation.
Product companies, scale-ups and enterprises in the UK, Western Europe and the US. A significant part of our work is in fintech and other regulated products; we also build for proptech, edtech and logistics. You can see examples in our portfolio and in case studies such as six years of product engineering for a UK property data platform.
We are a European nearshore team. Our engineers are based in Poland, we have offices in Warsaw and London, and we have a representative in Germany. Working hours overlap with the UK and the rest of Europe, so daily stand-ups, code reviews and calls run in real time rather than through overnight hand-offs. With clients in the US we agree a fixed overlap window before the work starts. If you are comparing vendors, see how to choose a nearshore software development partner.
Since 2012. Smartym Pro started as a small team of mobile developers; today we are a team of 50+ people and have delivered more than 80 projects. More about our history is on the About Us page.
Our core is enterprise Java and Oracle, modern web front ends, native and cross-platform mobile, and applied AI with large language models and agents. The stack for a specific system follows your constraints and the team that will maintain it. The full list of languages, frameworks, clouds and tools is on our approach page, and each expertise page goes into more detail.
Yes. This is a common start for modernisation and support work. We begin with an assessment of the code, architecture, infrastructure and delivery risks, then agree whether to stabilise the system, modernise it step by step or rebuild selected parts. Missing documentation is not a blocker: we reconstruct it from the code, the database and interviews with your team. More in application modernisation vs a big-bang rewrite.
Didn't find your answer?
Tell us what you want to build or change, and we will suggest the first steps.