# An Atlassian Cloud app built around the way your organisation works We build Atlassian Cloud applications for one organisation’s process, in Jira, Confluence, Bitbucket, Compass and Rovo, on Atlassian Forge inside your own Atlassian site. You get a rough price at the first meeting and an accurate one after the analysis. ## From your description to a release Simple and complex applications start the same way. A complex one adds a deep analysis and, where it needs them, a proof of concept and a senior UI/UX designer, before we write code. A simple application: Simple means the application works in one Atlassian product, connects to no system outside Atlassian, and is released in one go. A complex application: Complex means the application connects to systems outside Atlassian, works in more than one Atlassian product, or is large enough to release in stages. ### You describe the application Describe it in the estimate on this page, or in the [Submit application request](https://oktul.atlassian.net/servicedesk/customer/portal/35/group/72/create/84) form in our Help Center. We study it, prepare our questions and propose a time to meet. You receive: Our questions and a meeting time ### First meeting *Rough price* We show how we understand the problem, then ask how the work runs today. You leave with a rough price. You receive: A rough price for your case ### Analysis and plan *Accurate price, a simple application* We map the permissions, modules and backend dependencies the application needs, and draw its first screens. Then we present how the work will run once the application is in place. For a simple application, the price at the end of the analysis is accurate. You receive: The to-be plan and first screens ### Deep analysis *Complex applications · Accurate price, a complex application* We map every connection to your other systems: payloads, API endpoints, authentication and security. We also define the application’s structure and vision. The deep analysis costs about €720 and is included in the estimate. The price at its end is accurate. You receive: Connections, payloads, endpoints and an accurate price ### Proof of concept *Complex applications, when needed* When the solution is new, or when you ask for one, we build a small working version first to prove the approach. You receive: A working proof of concept ### Design and workshops *Complex applications, when needed* For an application with interfaces of its own, we recommend a senior UI/UX designer, who maps your users and the roadmap with you. We explain the risks of going without one, and the choice is yours. When the solution is still open, we run workshops. You receive: User personas and a roadmap ### First release, then the rest *Complex applications* What you need first goes into the first release, and the rest is planned into later ones, so your people start using the application sooner. You receive: A release plan ### Build Architects who know the Atlassian ecosystem write the application, using what we learned building our own. A complex application is built release by release. Every week or two we meet to show what is done, answer open questions and review the risks with you. You receive: A demo every week or two ### You test it first About a week before we finish, you start testing on your own Atlassian site, or on a demo site we provide, and note what should change. You receive: A test version to try ### Fixes We fix the bugs and cosmetic issues your testing found and, where it fits, add a small function you asked for. ### Release and handover You receive the production-ready application with documentation of its architecture and dependencies. We support the rollout and advise how to introduce it to your people. For a complex application we can also train your wider team in a session you may record. You receive: The application and its documentation ### Free fixes and the platform guarantee We fix bugs free for three months after release, or six for a complex application. If an Atlassian change breaks the application within six months of release, we treat it as a bug and fix it free, under our SLA. ### Support and the next feature We keep supporting the application. A new feature goes through the same steps, shorter. In the analysis and the workshops we share what worked for other organisations with a similar problem, without naming them or anything they told us. ## Built by Atlassian solution architects We spent years inside the Atlassian sites of banks and the public sector, where an application that mishandles a field causes an incident. Every release is tested as if it were going into a bank. - Company and credentials: https://oktul.com/about/ - Our own applications: https://oktul.com/apps/ ## How we build every application The same practice runs through our Marketplace applications and the ones we build for you. ### AI-ready from the first release What people record usually lands in Jira and Confluence, where your Teamwork Graph builds the context Rovo and your other agentic teammates answer from. An application that keeps its work elsewhere gets a Teamwork Graph index of its own, with each person’s permissions. ### Compatible as Atlassian changes We build each application to stay backward and forward compatible, as far as Atlassian’s changes can be foreseen. ### Security fixes within our SLA When a new vulnerability affects our applications, we fix it within our SLA’s resolution times. They follow the Atlassian Fortified programme, the highest standard Atlassian sets for apps. ### Reviewed against WCAG 2.2 AA We review every application against the WCAG 2.2 AA accessibility requirements. ### Time and materials, or a fixed price We recommend time and materials: it is more flexible, support continues without a new contract, and features get built sooner. It usually costs less than a fixed price, which has to cover the unexpected. ### Who owns the application **You own it.** We build it on your resources. You receive the application and its full source code. or **We publish it.** When other organisations need the same application, we may offer to build it on our resources and publish it on the Atlassian Marketplace. You pay only an agreed licence price, with a lifetime 20% discount, and get early access. We tell you which path fits your case after the analysis. Read how we handle data: https://oktul.com/trust/ ## Estimate your application To send us your estimate, we need only a description, your name and your email. You can also describe the application in the [Submit application request](https://oktul.atlassian.net/servicedesk/customer/portal/35/group/72/create/84) form in our Help Center. An estimate from your answers, not a quote. The actual price can be lower or higher. https://oktul.com/custom-development/#estimate · hello@oktul.com ## Questions about custom development ### How much does a custom Atlassian application cost? It depends on where the application runs and what it does. The estimate on this page turns your answers into a price range. You get a rough price at the first meeting and an accurate one after the analysis. For a complex application, the accurate price comes after the deep analysis, which costs about €720 and is included in the estimate. Training for your wider team is priced separately. ### Do you work on time and materials or at a fixed price? Both, and we recommend time and materials. It is more flexible, support continues without a new contract, and features get built sooner. It usually costs less than a fixed price, because a fixed price has to cover the unexpected. ### How much does yearly maintenance cost? It depends on the application and on how often the parts it uses change. We build each application to stay backward and forward compatible, as far as Atlassian’s changes can be foreseen. When a new vulnerability affects the application, we fix it within our SLA’s resolution times, which follow the Atlassian Fortified programme. ### Are there running costs on Atlassian’s side? Sometimes. A very complex application that you own, running on a site with many active users, usually 100 or more, may bring Forge platform costs for compute, storage and similar. We set them out after the analysis. ### Who owns the application and its source code? You do, when we build it on your resources. You receive the application and its full source code. When other organisations need the same application, we may offer to build it on our resources instead and publish it on the Atlassian Marketplace. You then pay only an agreed licence price, with a lifetime 20% discount, and get early access. ### Does our data leave our Atlassian site? Only where your case needs it. Every application we build runs on Atlassian Forge inside your own Atlassian site, where Atlassian stores the data. When the application has to exchange data with another system, we name the host in the application’s manifest and document what leaves, where it goes and why. ### What happens when Atlassian changes the platform? If an Atlassian change breaks the application within six months of its release, we treat it as a bug and fix it free, under our SLA. Other bugs are fixed free for three months after release, or six for a complex application. ### Can we test the application before it is finished? Yes. About a week before we finish, you start testing on your own Atlassian site, or on a demo site we provide, and note what should change. We fix what you find before the release. ### Why not build the application ourselves with AI? AI tools can write a Forge application’s code. A bank or ministry also needs permissions kept to what the application uses, data kept inside Atlassian, answers for its security reviewer, documentation, and someone who fixes the application when an Atlassian change breaks it. Our process covers each of those. Our guarantee covers platform changes for the first six months. ### Can you build Rovo agents and Flow steps? Yes. A Forge application can add a Rovo agent with the actions it may take, and custom steps for Jira flows. Choose Rovo or Flow steps in the estimate to see what they add. --- ## Published by - Oktul OÜ - Oktul OÜ · Reg. nr 17589681 · Tallinn, Harjumaa, Estonia - Email: hello@oktul.com - Web: https://oktul.com/ - Atlassian Marketplace: https://marketplace.atlassian.com/vendors/534484195 - LinkedIn: https://www.linkedin.com/company/oktul - YouTube: https://www.youtube.com/@OktulDevelopment - Estonian: https://oktul.com/et/