Mobile & SaaS
POI369 is a Tallinn-based studio that designs and builds SaaS products with user accounts, subscriptions, roles and integrations. iOS and Android apps are scoped per project. The app, the web dashboard and the API behind them come from the same team, and store release is part of the work in the proposal. POITIM, the SaaS product we built end to end, is live in five languages. Pricing is by scope, with a written proposal.
Last reviewed September 26, 2026 · Reviewed by Ahmet Bulut
Apps that use what the phone offers: camera, notifications, location and offline use. Which platform ships first is decided with you, based on your users.
Where it fits, shipping to both stores from one codebase is an option. Native or cross-platform is decided in discovery, together with the scope.
The web app your customers sign in to and the admin panel your team runs the business from. For POITIM we also built a macOS and Windows desktop client.
Google or email sign-in, a role and permission matrix, and a multi-tenant backend that keeps each customer’s data apart. How data separation is tested is written into the scope.
Monthly and yearly plans, trials, credit or token wallets, store purchases and card payments. Who is entitled to what is managed in one place.
Connections to calendar, CRM, messaging and accounting tools, plus the product’s own API and webhooks. When a third-party service fails, the flow does not stop silently.
Assistants, recommendations, interpretation and classification. The model only sees data the user is allowed to see, and cost and quality are measured.
App Store and Google Play accounts, store listings, review, test builds and updates. Crash reporting and notifications are planned with the scope.
If the goal is to present the brand, collect leads or sell products, you most likely need a website, and we build those at package prices under Web Design and Development. This page is for products people sign in to and come back to: mobile apps, subscription software, customer portals and internal business tools.
A mobile app is not always the first step. If most users sit at a desk, starting with a web app and moving the proven flows to mobile later can be cheaper and faster. If notifications, camera, location or offline use are central, the app is planned from the start. We give this recommendation in writing, with the reasons, during discovery.
Teams with a clear idea who want to reach first users with a working product. Scope is cut down to the flows the first version really needs.
Companies managing orders, bookings, field teams or customer requests through spreadsheets and chat groups. The process moves into one data model.
Businesses with a website that want customers to manage accounts, orders or memberships from their phone.
Teams moving from one-off sales to monthly plans, trials or credits. Entitlements and the payment flow are built together.
Apps whose developer left, that cannot be updated or that are stuck on store policies. We review an existing app before taking it over, then propose a plan.
Teams that want an assistant, recommendations or automatic classification in an existing product. Data access is scoped first, then the feature is built.
B2B team-operations platform we built from zero: multi-tenant backend, Google sign-in, role and permission matrix, web app, self-updating macOS and Windows client, the Timo AI assistant, ClickUp, Google Calendar and Telegram integrations, five languages.
poitim.com
Read the case study →Consumer platform we built end to end: user accounts, token wallet and payment flow, a per-category AI interpretation pipeline and performance work for the mobile devices most readings happen on; six languages.
faltastik.com
Read the case study →No-code integration platform: visual flow builder, ready-made connector catalogue, real-time monitoring and automations that recover from failures. Brand, product interface and site by us.
www.poicloudsync.com
Read the case study →Who the users are, which flows the first version needs, which platforms and integrations. The result is a written proposal with scope, price and timeline.
A prototype of the main flows, in a format chosen to fit the scope. The aim is to see how people use the screens before code is written, and trim scope if needed.
App, API, database and dashboard move forward together. You follow progress through test builds and a preview URL.
Testing across devices, security and permission checks, store listing and review. Crash reporting and analytics setup is planned within the proposal.
Post-launch maintenance is planned separately: operating system updates, security patches, monitoring and backups. New features are scoped separately, based on real usage.
There is no catalogue price, because cost depends on the number of platforms, screens and flows, integrations, the payment model and the admin panel. After a short discovery call we send a written proposal priced by scope, listing exactly what is included.
It depends on scope. Once the first version’s flows, platforms and integrations are clear, the timeline comes in writing with the proposal. Store review times are outside our control, so the release date is planned with room for review.
Ownership and accounts are written into the proposal. Who holds the source code, store accounts, domain and server access, and how they are handed over, is settled before work starts.
Post-launch maintenance is planned separately. iOS and Android change every year, store policies change and dependencies age, so an app needs maintenance after launch. The scope and fee for maintenance are written into the proposal.
Yes. Developer accounts, store listings, screenshots, privacy disclosures, test builds and the review process are part of the work in the proposal. Whose name the accounts are opened in is written into the proposal. We cannot make the store’s decision; fixes after a rejection are also part of the work in the proposal.
Yes. Before taking over an existing app we review the code, infrastructure, security and store status, then give you findings and a recommended path in writing: continue, rewrite specific parts, or migrate. The decision is made with you based on that review.
Global B2B team management platform, built end to end from brand identity to the desktop app, in five languages.
AI-integrated fortune telling and astrology platform across 6 languages.
No-code SaaS integration platform for SMEs: connects CRM, ERP, e-commerce and accounting tools with drag and drop.
Tell us who it is for, what the first version must do and which platforms it needs. We come back with scope and a written proposal.
