Remplate
Operational journeys
A marketplace with several types of users, checks, scheduling and API connections.
View projectGet your software project moving again
Understand what is stuck. Stabilize what matters. Move forward with a clear next step.
Have my project reviewedExplore the workAn incomplete journey, fragile integration or unstable deployment is holding your project back. CHRD examines your website or application to decide what to keep, fix or replace, based on its actual condition.
A product exists. The next step is unclear.
A live application, Replit prototype, AI-built product or interrupted project: diagnosis comes before changes.
- An important function remains blocked or unreliable.
- The product is slowing down and each change creates another problem.
- Your provider is changing and documentation is missing.
- You have a prototype without a clear view of what remains before launch.
Our technical work in context
These projects illustrate our design and development work. They are not presented as recovery engagements.
River Ault
Data and access
A specialized product with structured information, user states, access controls and exports.
View projectFrom assessment to recovery
The first intervention depends on symptoms, access and risk to your users.
Technical audit and product assessment
Review code, dependencies, journeys and deployment. Separate findings from questions that need investigation.
Stability and integrations
Reproduce errors and repair priority connections, with attention to access and data.
Performance and user experience
Identify what slows pages or operations. Verify fixes against the affected tasks.
Completion and evolution
Finish a workflow, prepare a launch or gradually replace a part that is difficult to maintain.
The assessment delivers findings and priorities. Fixes and new features are scoped and priced separately.
When the problem lies between tools, explore our work on automation and integrations.
Fix, restructure or rebuild?
We first look for what can be kept. Options are compared by effort, dependencies and the service that needs to stay available.
- Fix a specific area
- The foundation meets the need and the problem can be isolated.
- Restructure progressively
- The product works, but parts of it hold back further development.
- Replace what blocks progress
- One part no longer supports the need. Its transition is planned.
If a new part of the product needs to be built, explore our approach to custom software and portals.
Recovery in manageable steps
Describe and reproduce
Describe symptoms, critical workflows and authorized access.
Assess the current state
Present findings, uncertainties and priorities.
Work in stages
Prepare backups and rollback. Fix and verify in a test environment.
Release and hand over
Organize release and document changes and monitoring needs.
Understand before estimating
Code quality, dependencies and the workflows to preserve determine the work. A description helps scope the assessment, but may not price every fix.
A paid assessment can be a separate first engagement. Scope, deliverables and price are agreed before work begins. Further work follows the findings.
A clear agreement before we begin.
- The investment
- The proposal separates creation, third-party services and support. Displayed prices are in Canadian dollars (CAD), unless stated otherwise.
- What you receive
- Deliverables, access, ownership and acceptance criteria are defined in the agreement.
- The first step
- A conversation about your needs. If the project requires further study, we propose paid scoping with defined deliverables.
Your project recovery questions
Can you take over an AI-generated or Replit application?
Yes, after reviewing the code, access and behaviour. The tool used to build it does not establish its quality or what can be kept.
Do you need the source code for the first conversation?
No. A description, screenshots or a demo are enough for the first conversation. Diagnosis then requires authorized access. Do not send passwords through the form.
Can the website or application stay live?
That is a goal to assess against testing, backup and deployment options. Any necessary interruption is planned and communicated.
How does changing providers work?
We identify the code, access, hosting, domains and documentation to retrieve. Rights and obligations must be clarified before the transition.
Do you always recommend rebuilding everything?
No. We look for what can be kept. If rebuilding is preferable, we explain why and prepare the transition.
Where is your project stuck?
Describe the problem and the next milestone. A link or screenshot can help.
Have my project reviewedNo commitment for the first conversation. We clarify the need before proposing an engagement.