PromptFactory
Contact

PromptFactory · by PromptCompany

Software and electronics, built by AI agents. A human sets the tasks.

It works like ChatGPT, but the result is finished, tested code merged on main, not a chat answer. A human also sets the rules and decides wherever a gate asks.

For teams building software or electronics products. Each task goes from your backlog to code merged on main through fixed stages: build with tests, reviews, quality gates, and for larger tasks a plan and a proof stage too.

Talk to us about a pilot See how it works
The line: stages and gates
  1. Taskfrom the backlogYou set tasks and priorities
  2. PlanTHINK
  3. BuildBUILD
  4. Test and provePROVEred tests → another build round
  5. ReviewREVIEWreview findings → another build round
  6. Gatesqualitya human decides when a gate asks
  7. Merge to mainLANDING

How it works

From backlog to main, by the same rules every time

Each task goes through fixed stages, set by its size: small changes are built and reviewed; larger ones also go through a proof stage. A task is one change with its tests. AI agents work in roles; a human sets the tasks and the rules, and decides wherever a gate asks.

  1. 01 · TASK

    You decide what gets built

    You set the tasks and priorities; a task goes from the backlog onto the line.

  2. 02 · THINK, BUILD

    Plan and build

    AI agents in roles build the change, code and tests together; larger tasks get a plan first.

  3. 03 · PROVE

    Test and prove

    Tests matched to the change run during the build and, for larger tasks, again as proof; the full battery runs every night. A red test means another build round.

  4. 04 · REVIEW

    Review and gates

    Every change is reviewed by an AI model; larger code changes and every risky change get a second review by a different model. Review findings send it back for another build round. Then the quality gates, and the merge to main.

    When a gate asks, a human decidesfor risky changes, the owner can also veto

Every step is recorded in an append-only, hash-chained ledger.

Each stage has exactly one allowed next step, and all merges go through a single queue.

A human in the loop. Questions for the human arrive as cards in the owner's console and app, voice included. A decision is one tap.

What it builds

Software and electronics today

Expanding into: mechanical engineering, systems engineering, cybersecurity and manufacturing.

Software

Embedded firmware, on-board software (ROS 2), backend services, web apps, AI models, simulation, CI/CD.

Electronics

Printed circuit boards as code, in atopile and KiCad, with the BOM generated from the design.

AI agents design the boards in sessions with an engineer.

Reference project

The factory's core runs every day on a reference project, an autonomous drone-inspection system, where it works on:

  • Autopilot and navigationembedded software, C/C++, Zephyr RTOS
  • Mission computer and ground stationsROS 2
  • SITL simulationflight in the Gazebo simulator
  • AI perceptionwind turbine blade inspection; PyTorch, ONNX
  • Backend servicesFastAPI, gRPC, PostgreSQL
  • API contracts and SDKsProtobuf; SDKs generated from the contracts
  • Web and desktop applicationsTypeScript, React, Next.js; Qt/QML
  • CI/CD and end-to-end testsPython; Docker, GCP, Robot Framework
  • Electronicsthe autopilot family and modules: sensors, power, networking

Test tools

  • pytest
  • GoogleTest
  • Vitest
  • Jest
  • Playwright
  • Docker Compose
  • Robot Framework

Pilot

Run a pilot on your own project

The core of the factory is running today. We are looking for partners to prove it on their own project.

  1. Onboarding

    1 · ABOUT 2 WEEKS

    A front-engineering workshop on requirements, backlog and architecture, then a copy of the factory set up for your project.

  2. Factory run

    2 · 2–4 WEEKS

    The factory delivers tasks from your backlog.

  3. Results

    3 · AT THE END

    A review of the features delivered, the measurements, and a pilot report.

WHAT YOU BRING

  • a project or repository
  • one person on the product side
  • about 2 hours a week

WHAT YOU GET

  • the features delivered in the pilot, merged on main
  • the measurements from the run
  • a pilot report

This is the proposed shape of a pilot; we agree the details on a call.

Write to us about a pilot
PromptCompany

Contact

Next step: a short call

Tell us what you are building and we will set up a short call about a pilot.

Email

office@promptcompany.ai

Maciej Kmet · PromptCompany (AISolar sp. z o.o.)