progwise
The next chapter of building software
You shape. Agents build. Experts guide.
A shared platform for developers and their customers to create, maintain, and evolve software with AI.
Software development is becoming a business-driven process. The people who know the business decide what the software should do. Developers and designers are the experts they bring in.
The platform is in development at Progwise. This is the experience we’re building.
Our ambition is a first version in days, followed by years of continuous improvement, with lower delivery and maintenance costs.
Your projects. Your customers. One shared process.
For developers and software companies
Run your customer projects in one place. Code, pipelines, and deployments are hosted on the platform, built on Git. Set the engineering standards once, invite customers and designers, and bring your expertise where it’s needed.
We’re starting with a few supported tech stacks, so agents, pipelines, and deployments work the same way in every project. Bring existing projects with their full Git history.
For business people and designers
Describe what you need in your own words. Your AI consultant asks questions, suggests ideas, and prepares decisions you can approve, decline, or refine. Your development team handles technical choices and explains their impact on cost and timing.
From the first request to the next release.
The same steps take a project from its first version through every improvement. Everyday changes stay in the business team’s hands, without hiring a developer for every amendment.
- Start the project. The developer sets the engineering rules and invites the customer.
- Request. Describe a need, a problem, or an idea. The AI consultant asks questions and proposes an outcome.
- Agreed work. Agree what will be done and what counts as done. Waiting for a decision or funding? Work resumes when it’s available.
- Change. Agents build it, run the checks, and prepare a preview. The customer approves the outcome; developers review the code where required. Needs revision? The same change is updated and reviewed again.
- Release. The approved change goes live and is recorded. The next improvement starts again at Request.
Archive the project. Active work ends. Decisions, changes, and release history are kept.
For developers: agreed work is an issue, and a change is a branch and pull request. The pull request is merged after the customer approves the preview and any required code review is complete.
How we plan to protect existing software and data
Limited agent permissions, isolated previews, automated tests, and specialist review provide safeguards. Backups, tested data migrations, and verified recovery procedures protect existing data. Release plans cover monitoring and recovery for both software and databases.
Meet in the project office
Meetings take place in a shared virtual office with rooms and people you can walk up to. Review previews together and turn conversations into recorded decisions and work.
Keep control of spending
Project work is funded monthly in advance and starts after payment. The platform tracks spending, updates forecasts, and warns when funds run low. Chargeable work pauses when funding runs out, and additional spending needs your agreement.
Project funding is separate from the platform subscription. Platform pricing is still being developed.
Help shape what comes next.
Build software for customers, or shape the tools your business uses? We’d like to hear how you work.
[email protected]