The build keeps moving, the scope and revision trail does not.

Rocketly is the CRM layer for the commercial and communication process that runs from a project enquiry to a maintenance agreement: requests from connected channels attach to a client record, scope and proposals are documented, revision rounds are counted as tasks, and maintenance and renewal dates are surfaced as reminders. Your code repository, issue tracker and hosting panel keep running in parallel.

You standardize the discovery note with a document template and build the scope list on top of it. In the proposal module you write items as day rates, packages or milestones, share them as a PDF and follow view and approval status from the record. An approved proposal is tied to the contract, and because out-of-scope requests carry their own tag, the conversation about an additional proposal rests on written records.

Yes. Every sprint and every revision round opens as a task group, keeping the requester, the date and the content on the record. When the contracted round count is reached, an out-of-scope tag is added and an additional-proposal task is created. That turns the question of which round you are on into a matter of record rather than memory, and keeps the client conversation on concrete items.

No. Your repository, version control, issue tracker and deployment pipeline keep doing their job. Rocketly is the commercial and communication layer above them: enquiry, scope, proposal, contract, revision counting, maintenance agreement and client threads live here. Where you need information to move between the two sides, webhook and Zapier connections are available.

You define monthly maintenance lines with a recurring proposal, and each period opens the same task set. A bug report from the client reaches the project record through the support channel, gets a priority tag and is assigned to an owner. Because work inside the agreement is tagged separately from extra development, the end-of-period billing conversation is already settled by the record.

Yes. You enter renewal dates on the client record and build the reminder flow in Workflow Builder; 55 templates and 46 trigger types cover date-based flows like this. As a date approaches, a task opens for the team and a notice draft is prepared for the client. The provider performs the renewal itself; Rocketly carries the reminder, the follow-up and the thread.

Yes. The same structure works for one person: enquiry records, proposals, contracts, revision counts and maintenance reminders sit in one panel. As the team grows you add users, define roles and limit who can reach which project. The task and reminder flows stay the same; only the number of people carrying them changes.

The interface is available in 3 languages — Turkish, English and Russian. You run client threads in the language you choose, note the time zone and correspondence language on the record, and plan delivery and meetings around it. Proposal and document templates can be maintained separately per client language.

There is a permanently free plan and no credit card is requested at sign-up. AI features, advanced workflow structures and some channel connections sit in paid plans. A small studio can set up enquiry and proposal tracking on the free plan and move up as it grows; the pricing page lists which feature belongs to which plan.