Programming
Not every extension needs a project. An extra field with validation, a CSV export, a script that reconciles data every morning, a new endpoint for the partner API: we build tasks like these in your existing code — on a separate branch, with tests, as a pull request you review and merge. Anything bigger we split with you into several tasks, each with its own acceptance criteria.
Describe your development task →Typical tasks
- Script for a recurring task (Python or Node.js)
- New feature in an existing web app
- REST API endpoint with validation and documentation
Every task runs on your board in the Prozess-Abo: with acceptance criteria, delivered 48 hours after we start it — counted Mon 8 am to Fri 4 pm; over weekends and public holidays the clock stops. The first task is free. Scope per task in the service catalogue →
Example acceptance criteria
When we start a task, we record its acceptance criteria on the card. You measure acceptance against them — if a delivery doesn't meet them, we revise it at no extra cost until it does.
- 1The described feature behaves as specified in the agreed cases
- 2Build and existing tests pass, new tests cover the change
- 3Change delivered as a pull request with a description
- 4No credentials in the code
What you get
- Built in your repository, not in someone else's system
- Separate branch and pull request — you decide whether to merge
- Tests for what's new
- Short documentation in the code and the pull request
Technologies
TypeScript, Node.js, Python, Next.js, PHP, SQL
Describe your first task — it's free.
Create your workspace and put the task on your board. Before we start, we check that it fits into 48 hours (counted Mon 8 am – Fri 4 pm), and deliver it with acceptance criteria.