Eriksen Labs

Forge builds · fixed scope, fixed price

Forge Extension Sprint for small Atlassian gaps

Small Jira, JSM or Confluence gap? Eriksen Labs builds focused Forge extensions for Solution Partners and teams.

Email a description For Solution Partners
Built on
Atlassian Forge, hosted by Atlassian
Products
Jira, Jira Service Management and Confluence Cloud
Length
Typically 1–3 weeks
Price
From EUR 6,000 per one-week build
Payment
50% at scope, 50% when the tests pass
Reply
Normally within two business days

Principles

The aim is a small extension that does one thing properly and that someone other than its author can maintain. Neither you nor your customer should end up owning an internal Forge product forever because a gap needed closing once.

This is not broad consulting, and it is not an implementation project without an end. If Jira, Jira Service Management, Confluence or Automation can already close the gap, you are told so during scoping, and nothing gets built.

  • Forge first

    Built on Atlassian Forge and hosted by Atlassian. Eriksen Labs runs no server for it.

  • Narrow scope

    One gap, one extension. The scope fits on a page and says what the extension will not do.

  • 1–3 weeks

    Typical, where the scope allows it. Bigger work is split into separate sprints or declined.

  • Partner-led

    When a partner brings the work, the partner keeps the customer relationship. Eriksen Labs builds, documents and hands over.

Where it helps most today

Four kinds of work fit the format well at the moment.

Connect to Forge

Private Connect apps that must move to Forge

End of support for private Connect apps begins

After Atlassian's end of support for private Connect apps begins, Atlassian addresses only critical security vulnerabilities in Connect, Connect features can be deprecated at short notice, and apps left on Connect may not keep working as expected. A small private Connect app, such as a panel, a webhook handler or a scheduled job, is often a single sprint on Forge. Where Forge cannot do what the Connect app did, that comes out in scoping, not halfway through the build.

Price: from EUR 9,000, fixed after the assessment

Rovo Studio and AI-built apps

Apps built with Rovo Studio or by AI, before production

Rovo Studio and coding assistants make a working Forge app quick to produce. Whether it is safe to run is a separate question. A review covers the manifest's scopes and egress, permission checks in every resolver, identity and project taken from platform context rather than from what the browser sends, storage and deletion of personal data, and error handling. You get the findings in writing and, if you want them, the fixes.

Price: from EUR 3,000

Jira Service Management

Portal and request flows

Actions and panels on the customer portal, extra steps around raising a request, and small request-flow changes the portal does not offer natively. Recurring Requests, Eriksen Labs' own JSM app, is built on the same portal extension points.

Price: a sprint, from EUR 6,000 per one-week build

Data stays in Atlassian

Builds that must keep data inside Atlassian

When a customer's security review rules out sending data to a vendor's servers, the extension is built on Forge with no external egress and its data in Atlassian-hosted storage, designed to meet the Runs on Atlassian requirements where the feature allows it. Eriksen Labs' own Mermaid Diagrams & Gantt and Recurring Requests carry the Runs on Atlassian badge on the Marketplace.

Price: a sprint, from EUR 6,000 per one-week build

Example jobs

Three made-up examples of the kind of work that fits a sprint. They show the format. They are not past clients.

Example

A private Connect app with a date to meet

The situation
A customer runs a small private Connect app: a panel on Jira issues and a webhook handler that keeps one field up to date. It has to run on Forge before end of support for private Connect apps begins.
The work
Scoping assesses the Connect app and settles what Forge can and cannot do. Then a fixed-price move to Forge, deployed under the customer's own Atlassian developer account.
Not included
New features beyond what the Connect app already did.
Price
Scoping EUR 1,000, credited in full if the build is ordered within 60 days. The move from EUR 9,000.

Example

An app built with Rovo Studio, before production

The situation
A customer has built a Forge app with Rovo Studio that sorts incoming requests. It works on a test site. Before it is installed in production, someone has to check that it is safe to run.
The work
A review of the manifest's scopes and egress, the permission checks in each resolver, where identity and project come from, and how personal data is stored and deleted. Findings in writing, and the fixes if they want them.
Not included
New features. Those are a sprint of their own.
Price
From EUR 3,000.

Example

One missing step on the service portal

The situation
A partner's customer wants portal customers to add a structured follow-up to an open request, such as a date and a choice from a short list, instead of a free-text comment.
The work
Scoping first checks whether request forms or Automation already cover it. If not, a portal action on the request page that writes the answer to the request, handed over with source and documentation.
Not included
First-line support for the customer's users, which stays with the partner.
Price
A sprint, from EUR 6,000 for a one-week build.

How a sprint runs

Five steps, the last one optional. The two payments are marked where they fall.

  1. Free, 30 minutes

    First call

    A short call, or notes by email if that suits you better. You describe the gap, what the customer has tried natively, and any existing app or prototype.

    If the work is not clear yet, it goes to paid scoping (EUR 1,000) before any fixed price.

  2. Before any build

    Fixed scope and fixed price

    A written scope of about a page: what the extension does, what it does not do, the Forge modules and permission scopes it needs, how it will be tested, and the price. Nothing is built before you agree to it.

    50% when you accept the written scope

  3. Typically 1–3 weeks

    Build

    Built and tested on a development site, with working builds to try along the way rather than status reports.

    50% when the extension passes the tests written into the scope

  4. At the end of the build

    Handover

    The source code, a short technical document, and instructions for deploying and upgrading it. The app is deployed under the Atlassian developer account you or your customer choose, so it never depends on Eriksen Labs' account.

  5. Optional, yearly

    Maintenance, if you want it

    Optional, and agreed separately. What it covers and costs.

Price

Each sprint has a fixed price, set in the written scope before work starts. It changes only if the scope does, and only when you agree to the change.

Four offers, in order of starting price

  1. Scoping

    Fixed fee EUR 1,000

    For work that is not clear yet, including an assessment of an existing Connect app.

    Credited in full if the build is ordered within 60 days. Clear requests get a fixed quote after a free 30-minute call.

  2. Hardening an app built with Rovo Studio or an AI tool

    from EUR 3,000

    A review of scopes, egress, permission checks, identity, personal data and error handling before the app goes into production.

    Findings in writing and, if you want them, the fixes.

  3. Sprint

    from EUR 6,000

    for a one-week build (about USD 6,700)

    Bigger builds cost about EUR 6,000 per week of work. Typically 1–3 weeks, where the scope allows it.

    Bigger work is split into separate sprints or declined.

  4. Moving a private Connect app to Forge

    from EUR 9,000

    For a private Connect app that has to run on Forge before end of support begins on 31 January 2027.

    Fixed after the assessment.

Payment comes in two parts

You never pay in full for something that does not work.

50%

when you accept the written scope

50%

when the extension passes the tests written into it

Atlassian Solution Partners: ask for partner rates. Your customer stays your customer.

If the work does not fit a sprint, you hear that during scoping, with the reason.

Prices are in EUR and exclude any VAT. Invoices can be issued in USD, GBP or NOK on request.

Ownership and maintenance

What you receive

  • The complete source code
  • A short technical document
  • Instructions for deploying and upgrading it
  • The app, deployed under the Atlassian developer account you or your customer choose

On payment, ownership of the code passes to you or to your customer, whichever the scope names. The extension contains no licence check, remote switch or service hosted by Eriksen Labs, so it keeps working whether or not Eriksen Labs is involved afterwards.

Without a maintenance agreement, the handover documentation is written so that you, your customer or another Forge developer can take the extension over.

Maintenance, if you want it

20% of the build price per year

Minimum EUR 1,500, paid yearly. Cancel any time before renewal.

It keeps the extension working as Atlassian changes Forge:

  • Platform and API updates
  • Security and dependency fixes
  • Fixes to what was delivered

Quoted separately

  • New features, as a new sprint
  • A rebuild, if Atlassian retires something and the extension needs one

Good fit, and out of scope

A good fit

  • One gap in Jira, Jira Service Management or Confluence Cloud that one extension can close
  • A small private Connect app, such as a panel, a webhook handler or a scheduled job, that has to move to Forge
  • An app built with Rovo Studio or an AI tool that needs a review before production
  • Actions and panels on the Jira Service Management portal, and small request-flow changes
  • A customer whose security review rules out sending data to a vendor's servers
  • A partner who wants to keep the customer relationship

Out of scope

  • Broad Atlassian consulting, estate-wide audits and licence reviews
  • Long implementation projects, and Server or Data Center to Cloud migrations
  • New Connect apps, and anything that needs a server Eriksen Labs would host and run
  • Server and Data Center apps
  • Rebuilding what Jira, Jira Service Management, Confluence or Automation already do natively
  • First-line support for the customer's users, which stays with you
  • Open-ended retainers without a defined scope

Start

Email

support@eriksenlabs.com

Eriksen Labs is a one-person company in Norway, so the reply comes from the person who would do the build. Replies normally come within two business days.

What to put in the email

  • The product: Jira, Jira Service Management or Confluence Cloud
  • What the customer is trying to do, and what they have tried natively
  • Any existing Connect app, Rovo Studio app or prototype
  • The date that matters, if there is one

Looking for an existing app instead? The partner page lists the three apps, when each one fits, and when native Jira or Automation is the better answer.