Product Development from Graz

Start small. Go live fast.

From the first release to a product that grows – for companies and start-ups across Austria.

Discuss your project → How your product comes to life ↓

A new digital product often starts with a long list of features.

It takes months until everything is ready. Only then does it become clear what users really need.

We go the other way: we build the core first, bring it to real users and develop the product further with their feedback, as a web app, a mobile app or both. We are involved in two products ourselves: NetCero and Campivio. We work from Graz for companies across Austria.

The first version contains only what the launch needs. It goes live early, and real usage shows what comes next. So your budget goes into features that people need, not into assumptions.

Approach

How your product comes to life

How we price →

v0 Idea

01 · Initial meeting

You tell us about your idea and your target group. We tell you openly what we recommend for the first version.

The product so far ProblemTarget groupSuccess measure
v0.1 Prototype

02 · Concept and prototype

We define the core of the product and make it tangible with a clickable prototype.

The product so far ProblemTarget groupSuccess measure Clickable prototypeUser test
v1.0 MVP Focus

03 · First release

The first version goes live, with real users.

After a few weeks to a few months

The product so far ProblemTarget groupSuccess measureClickable prototypeUser test Core featureLoginLive
v1.x

04 · Development in short cycles

Feedback and usage data decide which features come next.

The product so far ProblemTarget groupSuccess measureClickable prototypeUser testCore featureLoginLive FeedbackUsage dataNew features
v2

05 · Operations and growth

We run the product, keep it up to date and scale it with your success.

The product so far ProblemTarget groupSuccess measureClickable prototypeUser testCore featureLoginLiveFeedbackUsage dataNew features TenantsSubscriptions and paymentsScaling

Before and after

What this approach changes

specification_final_v3.docx

All features are fixed in advance in a specification.
Users see the product only after months.
Priorities are based on assumptions.
Login, tenants and payments are added later.
New features arrive in large, infrequent releases.

With this approach

The first version contains only the core and goes live early.
Users work with the product early and give feedback.
Priorities are based on real usage.
Tenants and payments are planned in the architecture and arrive when the product needs them.
New features arrive regularly in small steps.

Scope

What product development includes

Design thinking and MVP

We start with the problem and the people who have it, not with a list of features. We test assumptions in conversations and on prototypes, and we abstract: the wish of a few customers becomes the core that many need. From this we derive the MVP, as small as possible and as useful as necessary.

UX design and prototypes

Clickable prototypes show early how the product works. We test them with future users before we develop.

SaaS foundations

We plan tenants, login and roles as well as subscriptions and payments from the start. So the product does not need a rebuild when the first paying customers arrive.

Operations and further development

We put the product into operation, monitor it and ship new features regularly. The infrastructure grows with the number of your users.

How we work

Methods we use to develop products

Design thinking

We start with the problem and the people who have it, and develop solutions in short loops of idea, prototype and test.
Abstract thinking

We separate the wish of individual customers from the problem that many have. This way you get a product and not a one-off solution.
User interviews

Conversations with future users show how they work today and what they miss.
Lean startup

Build, measure, learn: each version tests an assumption, and the result decides the next step.
Usability tests

Real people use the prototype. We change what they do not understand before it gets expensive.
Usage data

After the launch, data shows which features people use and where they drop off.

References

Products we are involved in

NetCero is an AI-powered SaaS platform for ESG management and greenhouse gas accounting, in which dectria holds a stake. dectria built the first prototypes; NetCero GmbH develops and runs the platform.

More than 100 customers and partners
AI-powered automation with Azure OpenAI
NetCero GmbH is ISO 27001 certified

Visit website ↗

Campivio is a platform for booking and access at campsites, a joint project of dectria and innoprojekt. dectria develops and runs the software.

Online booking and access via QR code
Payments to the campsites via Stripe Connect
Web platform on Next.js

Visit website ↗

FAQ

Questions about product development

What is an MVP?

MVP stands for minimum viable product: the smallest version of a product that real users can work with. It shows early whether the idea works and what matters next. So you invest in features that people need.

How long does it take until the first version?

That depends on the scope. First prototypes are often ready within a few days, an MVP takes a few weeks to a few months, depending on the scope. After the concept, we give you a concrete schedule.

What does developing a product cost?

That also depends on the scope. We usually work with an agile fixed price: you receive a binding offer with clear work packages and can change priorities within the packages. A small first version also keeps the budget for the launch small.

What does a SaaS product need?

Besides its actual features, a SaaS product needs tenants so that each customer's data stays separate, a login with roles and usually subscriptions and payments. We plan these foundations from the start, because a later rebuild is expensive.

Web app, mobile app or both?

Many products start as a web app, because it runs on any device without installation and ships fastest. As a PWA, it also runs offline. A mobile app follows when the product needs device features, has to sync data in the background or must be found in the app stores.

What does design thinking bring to product development?

Design thinking starts with the problem and the people who have it. Instead of working through a list of features, we talk to future users, build prototypes and test them early. Abstraction comes on top: we separate the wish of a single customer from the problem that many have. This way you get a product and not a one-off solution.