Project Setup
& Software Factories
Start a project with working engineering foundations, or build a repeatable delivery process across an existing team. Connect code standards, CI/CD, infrastructure, planning tools, AI assistance, and release controls.
The work
A foundation for one project or a repeatable team process.
Project kickstart
Start your software project with a working codebase, delivery pipeline, infrastructure, and team workflow. Give your engineers a foundation they can build, test, and release from.
Software factory setup
Build a repeatable process from product requirements to tested software releases. Connect planning, development, AI assistance, review, deployment, and operation.
Planning and team setup
Define ownership, contribution rules, and the first delivery plan. Configure planning and documentation tools such as Linear and Notion when needed.
How the engagement works
For founders and teams starting a product or a new engineering project. Define the first useful release, team responsibilities, constraints, and acceptance criteria before selecting current, supported technologies. For a planned release, Production Readiness & Launch Support assesses the product, release process, recovery, and operating handover against agreed launch criteria.
For engineering teams and businesses building several products. Map the current process, identify repeated setup and manual work, and record a baseline for delivery time, failed releases, and rework.
Take an agreed product change through requirements, local setup, implementation, code review, automated checks, and deployment to the agreed environment.
Assign owners for decisions and operation. Compare the results with the baseline, record remaining gaps, and hand over the code, access, documentation, and open decisions so the team can continue.
Illustrative workflow
One change through the complete delivery process
- 01
Requirements
Record the requested behavior, responsible owner, and acceptance checks.
- 02
Build and assist
Use the agreed environment and tools to implement a bounded change.
- 03
Review and test
Review the change and its evidence. Run the required automated checks.
- 04
Release and measure
Release under the agreed controls and record delivery time, failures, and rework.
Illustrative engagement. Scope, deliverables, and acceptance criteria are agreed for each project.
What you receive
A setup your team can use and continue.
A working repository or shared project templates, with architecture decisions and local setup.
Code quality checks, agreed automated tests, and CI/CD pipelines.
Agreed environments, infrastructure, secrets management, and release and rollback procedures.
A delivery process map, initial plan, owners, and baseline measures.
Planning and documentation workspaces, contribution rules, and team handover.
AI development instructions with access, review, and approval rules.
One real change delivered through the process, with results and remaining gaps recorded.
Engagements & pricing
Clear starting prices.
Start with a defined review, workshop, or monthly service. We agree the scope, availability, deliverables, and final price before work begins.
Monthly service
Scheduled Software Health Reviews
From€750per month
- Scheduled checks for one application and one repository.
- One monthly report with reviewed findings and a prioritized action list.
- One 30-minute review with your technical owner.
Initial assessment and setup are quoted separately. Remediation and emergency response require a separate agreement.
Discuss this engagementStarting prices cover the scope shown. Other services and larger scopes are quoted separately.
Prices are in EUR, excluding VAT where applicable. Travel and third-party usage costs are agreed separately.
Before we start
Does every project need a monorepo?
Repository structure follows the product and team. A monorepo can help with shared code and coordinated changes. Separate repositories can suit independent ownership and release cycles.
Can you use our existing tools and cloud provider?
Yes. Review the existing setup and retain suitable tools. Agree any changes, access requirements, and provider costs before implementation.
What does a software factory include?
A defined process, reusable tooling, automated checks, and clear responsibilities for building and releasing software. The scope follows the team and products. People retain ownership of requirements, review, and release decisions.
Which engagement fits our team?
A kickstart prepares one project for development and release. A software factory improves a repeatable delivery process across an existing team or several projects, with shared tooling and measurement.
Contact
Discuss your delivery setup
Tell us your goal, context, and constraints. For a focused technical consultation, we agree the question, preparation, session scope, and written next steps before work begins.
Discuss your project