Quick Scan
Know where you stand
From150€
- Half-day review of code and hosting
- Top 10 risks, ranked
- 1-hour walkthrough call
You know your industry and you built something that works. We make sure it holds up when buyers start asking technical questions — with an independent engineering review, hands-on help, and a technical partner at the table when you sell.
Open your project in your AI coding tool (Claude Code, Cursor, Copilot…) and paste this prompt as it is. Your AI works everything out from the code, changes nothing, and leaves passwords and personal data out of the report. Email us the report and we’ll tell you honestly what it would take.
You are a senior software architect. This project was built by its owner, who is not a professional developer, with the help of AI tools. The owner wants to prepare it for production and for sale, with a focus on security and GDPR (EU standards). Your analysis will be sent to an independent software engineer, who will use it to estimate the size and complexity of the work and decide whether to take on the project. Rules: - Do NOT modify, move or delete any existing file. Analyze only. - Work out everything yourself from the code and configuration in this project. Do not ask me questions. - If something cannot be determined from the code, say so explicitly. Do not guess. - The report will be shared outside this project. NEVER include passwords, API keys, tokens, connection strings, customer data or other personal data. If you find any, give only the file and line where they are, never the value. - Write so that a non-developer can follow: explain technical terms briefly the first time you use them. Write one report covering: 1. Summary: what the application does and for whom, as far as the code shows, and its main features. 2. Project size: languages used, approximate number of files and lines of code per language, number of database tables or collections, number of screens/pages and API endpoints. Rough numbers are fine; say how you counted. 3. Architecture: main components (core logic / engine, UI, backend, database), how they interact, tech stack, frameworks and key libraries. 4. Repository structure: key folders and files with a one-line description each. 5. Data flow: trace how data moves through the system step by step, from the moment it enters (user input, API, file upload) through processing, storage, and any output (UI, reports, emails, external services). For each step, name the files/modules involved. 6. External integrations: APIs, third-party services, AI models, and what data is sent to each. 7. Authentication & authorization: how it works, roles, session handling. 8. Security posture: secrets in code or config files, encryption at rest and in transit, input validation, logging, outdated or vulnerable dependencies (run the read-only audit tool for this stack if available, e.g. npm audit, pip-audit, dotnet list package --vulnerable). 9. Hosting & deployment: where and how the application is (or appears meant to be) hosted, configuration and environment handling, and anything that blocks a production deployment. 10. Quality & maintainability: automated tests and rough coverage, version control, CI/CD, documentation, code duplication, overall code consistency. 11. Technical debt: shortcuts taken for the demo that are critical before production. Include Mermaid diagrams: - A component/architecture diagram. - A data flow diagram showing every step from entry to output. - A sequence diagram for the most important user flow you identify. Then give a prioritized list of the top 5–10 risks (security, GDPR, production readiness), each with severity (High / Medium / Low) and a one-line suggested fix. End with a complexity assessment: overall size (Small / Medium / Large), code quality (Good / Fair / Poor) and production readiness (Ready / Needs work / Major work), each with a one-line reason, plus the 3 areas that will need the most work. Save the complete report as one Markdown file named project-analysis.md in the root of the project. This is the only file you may create. Then tell me the report is ready.
project-analysis.md in your project.You show us what you built and who you want to sell it to. Free, no commitment.
You give us read access to the code, a test version of the app and a description of the hosting. Under NDA if you want.
A written report with findings ranked by risk and a clear list of what to fix before selling.
You fix the issues, with our guidance or with us doing the work. We check the fixes.
You receive the validation statement, and we join your sales conversations from here.
Every package starts with a free intro call. The price is agreed upfront, before any work starts.
Know where you stand
Ready to show buyers
Build and sell it together
We go through your code, database, hosting and security. You get a clear report: what’s solid, what’s risky, and what to fix first, in plain language.
We help you, or your AI tools, fix what the review found, and explain each change so you understand your own product.
We join demos and buyer meetings as your technical partner and answer the security, architecture and data questions with you.
A dated “Independently reviewed by Duraware” statement for a specific version, with the scope of what was checked. Something you can show customers.
For products worth growing: we contribute as engineers on the project, paid per project or in exchange for a share of sales.
The validation statement names the exact product version, the date of the review and what was checked. It doesn’t claim more than was reviewed, which is exactly why buyers take it seriously.
New major version? A short re-review keeps the statement current.
Tell us what you built. You’ll get an honest first opinion in a free 30-minute call.
Email info@duraware.be