Have a project idea? Request a quote
Send the scope and the deadline, and a fixed-price estimate comes back within 48 hours with no obligation to proceed. The team is in Spain and Ukraine: a full working day overlapping London, mornings with New York, and an agreed window for Sydney.
Phone+34 634 839 752
Emailinfo@smart-ui.pro
Head officeCalle Los Maestros 10, Merida, Spain 06800
Send the scope, the deadline and what it has to connect to. A fixed-price estimate and a delivery plan come back within 48 hours, with no obligation to proceed. If it is easier to talk it through first, the numbers below reach the same people.
Questions we get before a project starts
Web applications and the backends behind them, AI agents and workflow automation, headless CMS builds, and QA. The usual starting point is a scale-up replacing something that no longer holds up, an agency that needs a white-label team, or a company automating a process that people still do by hand. 315 projects since 2018, for clients in the UK, US, EU and Australia.
Landing pages and MVPs: 2 to 4 weeks.
Custom sites, e-commerce and dashboards: 4 to 8 weeks.
Platforms with real integrations: 8 weeks and up.
An AI automation pilot is fixed-price and lands in 2 to 4 weeks. Every estimate comes with a milestone plan, and you see working software on a staging URL every two weeks rather than a status report.Most work is fixed-price against a written scope, so the number is agreed before anything is built. Longer engagements run on a monthly team rate. AI audits are fixed-price, from £2,500 for UK clients and $3,000 for US clients. Send a brief and an estimate comes back within 48 hours, with no obligation to proceed.
Bug fixes, monitoring, security updates and new features, on a plan sized to the project rather than a standard retainer. Repositories, servers and third-party accounts are in your name from day one, so nothing is locked to us and you can move the work to another team without asking us for anything.
Every project gets a review at handover and again on a schedule, because a project that was clean in March is not automatically clean in August. It covers where every key lives and what it can do, access to servers and repositories, exposed ports and old staging environments, dependency vulnerabilities, spend and volume alarms on metered APIs, and a backup that has actually been restored rather than assumed.
Yes, and it usually does. Small changes fit inside the two-week cycles at no extra cost. Anything that changes the shape of the project is re-estimated in writing before work starts on it, so the number never moves quietly and you decide whether it is worth it.