Bugs & regression tests
Fix a reproducible bug and add the test that keeps it from returning.
Autonomous Backlog Sprint · For teams and agencies
Turn overdue tasksinto accepted work.
Bugs, missing tests and upgrades keep competing with your product roadmap. Give us a defined slice of your existing backlog: we run a 14-day paid sprint and deliver changes with tests and review evidence. Your team decides what to accept.
For software teams and agencies with roughly 5–50 developers, an active repository, a backlog and working CI.
Work worth taking off your plate
The work your roadmap keeps pushing back.
Maintenance in an existing repository—not a blank-page product build. Start with tasks you can describe, test and accept independently.
Tests & refactoring
Strengthen tests and simplify existing code without changing the agreed behavior.
Upgrades & migrations
Update dependencies or migrate a defined framework component against agreed checks.
CI & technical debt
Repair a brittle build, clean up a pipeline or address a scoped security finding.
How the sprint works
From agreed task to accepted change.
Select
Bring 30–100 candidate issues if available. Together we select around 10–20 suitable tasks; selection is not a promise to finish all of them.
Configure
We manually agree decision-makers, access, approval order, repository boundaries and budget for this project.
Execute & verify
Agents attempt the work. We check changes against the agreed tests and quality gates, recording failures and human intervention.
Review & accept
Your team reviews PRs and evidence, accepts or rejects the work, and retains merge and production approval.
The handover
Every result has a task, a change and proof.
Review the proposed change against its original issue. See which checks passed, what failed, what it cost and where a person had to intervene. Incomplete work stays visible.
Changes
A PR or patch linked to the original task, with scope and review notes.
Verification
Test results and relevant validation evidence, including failed checks.
Economics
Actual compute spend, elapsed time and human minutes per accepted task.
Unfinished work
Rejected, blocked and incomplete attempts, with reasons and remaining risks.
Work already built
Real projects. Concrete work.
From an expert platform to an industrial catalog: two examples of custom software delivery, with the implemented scope and project status made explicit.
Client & expert platform
II Tonya
- The task
- Bring client requests, expert selection and booking into one managed service.
- What we built
- A web platform and server-side core for bookings, consent, billing and referrals, with background processing and an audit trail.
- What you can verify
- Versioned application code, verification records and a deployed core with working health and database-readiness checks.
- Project status
- The platform core is deployed. Remaining integration dependencies are tracked separately from the implemented work.
Industrial catalog · 1C-Bitrix
PUMP Selector
- The task
- Help buyers and sales teams shortlist pumps by flow, head and catalog specifications.
- What we built
- A selector integrated into 1C-Bitrix: 41 product fields, seven filter groups and 131 imported HRS models. Staff edit products in the standard catalog interface.
- What you can verify
- A working selector on the test environment, matching checks and traceable catalog imports that preserve manual edits.
- Project status
- The selector is implemented and checked on the test environment. The recorded technical checks cover the catalog and selection workflow.
These projects illustrate our delivery experience, not a promise of a particular ROI, delivery time or fully autonomous execution. Their scope is separate from the 14-day backlog-sprint offer.
A paid pilot, not a subscription
A bounded pilot. Acceptance-led terms.
Plan €1,000–3,000 for a paid pilot covering one repository and a limited backlog. This is an indicative range, not a fixed quote or a subscription. We agree the deliverables, acceptance-linked payment terms and all cost boundaries before work begins.
- Specify the definition of done and who can accept each task.
- Agree setup, compute, taxes, budget cap and payment terms in writing, including how unaccepted work is treated.
- The 14-day window begins after scope, access and setup are agreed. No task count or savings are guaranteed.
Custom integration
Automation does the work. People hold the authority.
The decision-maker and approval structure is configured manually for every project. We agree the rules with your team; the factory does not invent them. A human approves the final production promotion.
Delivery roadmap ↗Your team. Your client. Extra delivery capacity.
For agencies, the pilot can support your own client delivery under an agreed white-label arrangement. We take on selected maintenance work—not your client relationship. This is additional engineering capacity, not a promise to replace developers.
Before you commit
What is an AI dark factory here?
A traditional dark factory automates industrial production. Here, AI Dark Factory refers to software engineering: agents attempt scoped repository tasks, with verification and human acceptance. We do not sell a physical manufacturing system.
Is this a self-service SaaS product?
No. This offer is a managed, paid backlog sprint with custom integration. An ongoing managed service and a self-service platform are later steps, conditional on repeatable results.
What if a task cannot be completed?
We record the failed or blocked attempt and its cost. We do not count it as an accepted task. Acceptance criteria, payment treatment and stop conditions are agreed before the pilot.
How do we start?
Choose a time on Calendly to discuss your repository, backlog, CI and desired outcome, or email us. A public repository link is optional. Do not send credentials or confidential code. We first assess fit; no production access or payment is requested by this page.
Start with one real backlog
Which backlog would you like off your team's plate?
Bring your maintenance priorities, repository context and CI setup to a pilot call. We will assess suitable tasks and discuss a paid sprint with explicit acceptance criteria. Keep confidential code and credentials out of the booking form.
Book a pilot call
Choose a time and complete your booking on Calendly. Email is an alternative; clicking alone does not book a meeting.
bpall@mail.ruDo not send credentials or confidential code.