2
platforms
The product was published in both the App Store and Google Play.
Anonymised case / external CTO
A cross-platform automotive product for the US market.
Gonenych led the full startup CTO scope: finding the client and delivery partners, negotiations and contracts, project management, feature review and publishing the application in both stores.
Discuss your processRecorded outcome
Figures from the internal completion material.
US
target market
The product logic and functionality were designed for the US automotive market.
90 days
delivery plan
The internal plan allocated 70 days to MVP and 20 days to testing and documentation.
3 months
warranty scope
The delivery documentation included correction of minor defects after handover.
Starting situation
What required a change.
The startup needed one accountable layer between the client, business task and delivery partners.
Product logic, architecture, stages, contracts and acceptance criteria had to be defined.
The mobile product had to work on iOS and Android for the US automotive market.
Delivery had to continue through testing, documentation and publication in both application stores.
Solution architecture
A controlled process, not a single tool.
Commercial and discovery
Client acquisition, stakeholder communication, task clarification and product framing.
Team and contracts
Finding delivery partners, agreeing roles and preparing contracts, stages and acceptance terms.
Product architecture
Authentication, personal account, vehicle database, administrative editing and the core application logic.
Project management
Work breakdown, delivery coordination, timeline control and client communication.
CTO review
Feature review, delivery feedback and control against the agreed product scope.
Release
Testing, corrections, documentation and publication in the App Store and Google Play.
Control and safety
A person remains at the critical decision point.
One accountable role
The CTO connected business context, the client, contracts, the team and technical acceptance.
Stage acceptance
Architecture, core functionality and testing were separated into stages with defined outputs.
Post-release scope
The documentation included a warranty period for correcting minor defects after delivery.
Evidence status
What the supplied package supports.
Evidence source: an internal delivery plan dated 28 May 2025 and a clarification from the project CTO dated 29 July 2026. The document supports the architecture scope, 90-day plan, two-store delivery, testing, documentation and warranty period. The CTO confirmed that the completed product was published in the App Store and Google Play.
Claim boundary
What is intentionally excluded.
The client, application brand, store links, financial terms and contract details are not published. The planned 90 days are not presented as actual elapsed delivery time without a separate completed-work calendar.
Your process
First capture the baseline. Then choose the tool.
The first conversation defines the task, data, cost of error and human control boundary.
Describe the task