A decision made in a workshop room costs a conversation, and the same decision found during the build costs a rewrite. Our software development consulting starts with a free discovery workshop, run by the engineers who then build the product.
Advice from the people who write the software
Four situations in which an outside technical view pays off before any code is written.
You know what the product should achieve, but the feature list is long and unranked. Building before ranking means paying for features that you later drop, and learning it at the first demo.
An investment, a takeover or a scaling plan depends on what the current system can carry. Guessing its state is the expensive way to find out, and the answer arrives after the decision.
The product has to talk to systems you do not control, and their limits set the schedule. Those limits are cheapest to find before the first sprint, on the first workshop agenda.
Whether a model can do the task on your data is a question to answer early. We run discovery for AI ideas with our own AI toolkit and test the idea before the build.
Seen in real projects
Technical audit
Skyfri in Oslo asked for a technical audit to show what to change in the process of building the product. It ran from 20 November 2023 to 7 January 2024, and the talks in Oslo produced a new project. Since January 2024 our engineers have worked inside the Skyfri team. The EMS has run in production since June 2024 and controls the batteries across 7 plants, more than 5 MWh in total, with more than 4 MW of battery power.
Fractional CTO
Maciej Sułek was Project Tech Leader on KYOTO in the first stage of the collaboration, and the team built the MVP. The collaboration resumed in 2024, and until December 2024 we developed the product in Scrum. Over three and a half years it grew from a UX/UI MVP into a battery management system (BMS) based on SCADA, which monitors and controls the flow of energy in real time.
Workshops with users
Planning workshops began in July 2025, and the requirements of the tender were divided into modules, each tied to a point of the specification. From September 2025 to January 2026, workshops and tests with Deaf and blind users produced around 30 UX and UI changes, among them a high-contrast palette and rejection reasons in Polish Sign Language. Production started on 20 April 2026, nine months after the first workshops.
Roles, rhythm and tools from the first workshop to the release, read in the order you need them.
A Project Tech Leader owns the technical side of the project, architecture and technical solutions included. Every project has one: the person with the most technical knowledge in the project, appointed by our CTO together with the heads of the frontend and backend teams. A Project Manager or Scrum Master keeps the schedule and the process, and a Business Owner takes part in the workshop.
A Product Owner or a decision maker confirms the scope, and you can take the Product Owner role yourself. The decision maker is in the room, so the scope and the order of the modules are confirmed at the workshop and the schedule of the next steps is agreed at the same table.
A Product Designer takes part in discovery as well. With your Product Owner, the designer shapes the product vision and writes the hypotheses to validate, and they become a roadmap and plans for product workshops. The designer also defines personas and maps user journeys, and the work happens in Miro, FigJam and Figma.
The Project Manager is usually the Product Owner or the Scrum Master of the project, never both. The Project Manager is responsible for the schedule, the priorities of tasks and the deadlines, and watches progress with corrective actions when needed. The Scrum Master runs the Daily Scrum, Sprint Planning, Sprint Review and the retrospective.
A change outside the agreed scope is blocked until you accept it. Risks are identified and escalated to the Business Owner or the Head of Delivery, and the Project Manager organises regular project retrospectives next to the Scrum events.
Each project has its own Slack channel, clear rules for communication with you, and meetings with an agenda and a kept timebox. When you prefer it, we work in your tools. At Skyfri that meant MS Teams, Outlook with accounts in the client's domain, Slack and the client's Jira, and at KYOTO Slack and the client's Jira.
Sprints, inspired by Scrum, cut the scope into parts delivered in a short and controllable time, and each ends with a release and a demonstration of the working part of the product. Every project has daily standups, peer review and code review, and tasks are written as user stories with story points. On Zeronest, an energy management platform, the same Order Group team has worked on the platform from the start, in one- or two-week Scrum sprints.
In the stabilization stage we perfect every area that decides whether the product meets the expectations of its users. When the stage is over and the first users have given positive feedback, the first version is deployed to the production environment. After the release we can monitor performance and analyse how users interact with the product.
At Enerace the team stays with the product through workshops, estimates, delivery, testing on staging, release and maintenance. Production monitoring sends alerts to the team on Slack, a separate staging environment runs on an anonymised copy of production, and the mobile app is updated to meet app store requirements. Regular upkeep keeps the platform on current versions, so it takes new modules without a rewrite.
The system lives in a shared React and React Native (Expo) repository, with code shared between web and mobile and CI/CD from the first weeks. Stage 1 went to the client for testing in September and October 2025. Stage 2, from February to April 2026, covered production infrastructure, security and performance tests, the WCAG audit, training for the client's staff and publication in the app stores.
Four ways to start a project with us
Each service has its own page with the scope and how to begin.
For an AI idea, product discovery with our own AI toolkit tests the proof of concept first.
The owner of a system orders an audit before an investment or a round of funding, before taking over a system from another vendor or team, or before scaling a product. The first conversation takes place in a free discovery call, and a kick-off follows. We work in your tools, propose solutions and agree the order of changes with you, and the decision after the audit is yours. Changes to an existing system go to legacy software modernization. The technical audit page has the details.
A written report with the order of changes.
A fractional CTO is an experienced technical leader who works with a company part time, sets the technical direction, decides on the architecture and guides the engineers. At Order Group, our CTO and a Project Tech Leader take the role inside a project that our team builds, next to the engineers who write the code. Maciej Sułek has been Project Tech Leader on Mudita since July 2022, an app store for the Mudita Kompakt phone and a platform for over-the-air (OTA) updates, and wrote the technical requirements himself. The fractional CTO page has the details.
Our CTO, Maciej Sułek, co-founded Order Group in 2013
The Project Tech Leader proposes technical solutions that fit your business goals and turns your functional and non-functional requirements into technical ones. The leader sets the code standards, runs code review, verifies the estimates and identifies technical risks. When opinions differ, the leader has the last word, and when a skill is missing, can propose a change in the team.
Fractional CTO servicesAn AI idea raises a question that a workshop alone cannot answer: can a model do this task well enough on your data? Discovery for AI products uses our own AI toolkit and ends with a proof of concept, so the idea is tested before the next stages begin, as it was for PSONI. For a product with AI at its centre, AI MVP development is the next step.
Not sure which of the four fits? Describe your situation in one message and we will point to the first step.
Selected work
Order Group is supportive and flexible, delivering high-quality results.
Order Group delivered astonishing work in a very organized way. They truly are a team worth trusting your project with!
Where to start
Pick the situation closest to yours. Each path starts with a free conversation and ends with a clear next step.
Which one sounds like you?
I have an idea but no scope
First step
One meeting with the engineers who would build the product. We sign an NDA before it, so you can describe the idea openly, and a written summary and a schedule of next steps follow. The scope is ranked with the decision maker in the room.
A system runs and a decision depends on it
First step
We talk about the decision you face, then hold a kick-off. The audit ends with a written report with recommendations and the order of changes, discussed with you at a meeting. The audit covers code, data, infrastructure and the delivery process.
Technical decisions stall in my project
First step
Estimates arrive that the business cannot verify, or technical risks sit in people's heads. Our CTO and a Project Tech Leader take the role inside a project that our team builds, and the way in is the free discovery workshop.
I have an AI idea to test
First step
Discovery for AI ideas runs with our own AI toolkit and ends with a proof of concept. For a product with AI at its centre, AI MVP development is the next step.
I have a scope and need a team to build it
First step
Discovery turns what you already have into a scope that the engineers who will build the product can plan from. The same team then continues into the build, so the decisions made at the table stay in force.
Product & discovery
Consulting and discovery, answered
The discovery phase is the stage before development in which a team settles what to build, for whom, in what order and under which technical constraints. It turns an idea into a scope the team can plan the work from. For a new product our discovery phase services are the first stage of the collaboration, and the same engineers go on to build it.
Yes. The workshop and the basic mockup or proof of concept prepared from it are free every time, and you leave with an estimate. Extended discovery is a separate, wider scope that can run for several months, as it did for PSONI.
It depends on the scope. Basic discovery is one meeting, and the opening workshop in one of our projects took three hours. The extended discovery for PSONI took about three months, with discovery sprints and sprints that tested a proof of concept with AI before the next stages.
At the end of basic discovery you hold a confirmed scope, a written summary, a schedule of next steps and an estimate backed by a basic mockup or proof of concept. Anything wider, such as journey maps, a clickable prototype in Figma, a backlog and user stories, belongs to extended discovery.
A clear idea still rests on assumptions about scope, integrations and priorities. The workshop checks them with the people who will build the product, and integration and technical questions are on its agenda. Checking them at the table is cheaper than finding them in the build.
It includes four services: product discovery workshops, a technical audit, fractional CTO services and AI product discovery. For a product built around AI, AI MVP development is the next step, and for an existing system we offer legacy software modernization. Each service has its own page.
A fractional CTO is a technical leader who works with a company part time. CTO as a service is the same role delivered by a firm, and a full-time CTO is employed by the company. Our model sits inside a project that our team builds, so the person deciding on the architecture works beside the engineers who write the code.
When a product has to be built and the architecture is still open. The same goes for estimates that the business cannot verify, technical risks that sit in people's heads and not in a plan, a team that writes code without shared standards or code review, and technical decisions that stall because nobody has the last word.
After the first version is deployed to production, we can monitor performance and analyse how users interact with the product. At Enerace the team keeps the platform on current versions through regular upkeep, and the stack went through major modernisations in 2022, 2023, 2025 and 2026. The build itself is described on the How we do IT page.
Yes. We sign an NDA before the workshop, so you can describe your product openly. The engineers in the room are the ones who later write the code, so you explain your business once. Some of our clients appear on this page by industry only, like the energy trading company.
No. Discovery fits any moment when the scope is uncertain: a new product, a new stage of an existing one or a first project with a new partner. Enerace, a long-standing client, held workshops again with later modules: the choice of architecture in 2021, invoice import in 2024, and new views and the PowerShift module in 2025.
You do. Copyright in the code transfers to you with each payment, for the uses listed in the contract. For each project we act as the data processor and you are the controller, and the contract names the uses that the copyright covers. The Security and GDPR page has the details of both.
Under a separate data processing agreement for each project, with Article 28(3) of the GDPR as its basis. Access goes through named accounts and AWS IAM Identity Center on the principle of least privilege. We report an incident within 24 hours at the latest, and after the contract we delete or return your data within 10 working days, confirmed in writing within 7 days.
Book a free discovery workshop through the contact form and describe what you want to build. We reply to the form within 48 hours on working days. The workshop is one meeting, and the estimate follows from it, so you can decide on the next stage with a clear scope in hand.
Karol Oponowicz
Co-founder & Business Owner
Your message goes to
Filip Szamborski
Co-founder & CEO
Your message goes to
Karol Oponowicz
Co-founder & Business Owner
Your message goes to
Paweł Zieliński
Co-founder & Business Owner
Thank you for your message.
We read every message ourselves and get back to you within 48 hrs on business days.
Something urgent? hello@ordergroup.co
SO FAR WE HAVE WORKED WITH BRANDS LIKE:
