A furniture order passes through managers, assemblers, and couriers. A production system keeps those handoffs connected so the order, materials, and delivery details can be followed together. The right scope starts with how your workshop actually works, including returns and remakes.
Send your task or a link. I’ll clarify the scope and next step.
Bring an example order, the steps it passes through, the people involved, and how materials and pay are calculated. Explain which records already exist and where delays or duplicate entry happen. We can then separate the first delivery from later additions. Any fit with the forthcoming SaaS needs discussion; no ready-to-use subscription or demo is promised.
Project example
Merwood is a working furniture production system connecting Kaspi orders to assembly and delivery, with workflows for managers, assemblers, and couriers. Its private application is not a public demo. A separate SaaS ERP for other furniture manufacturers is in development and has not launched; requirements and early interest can be discussed now.
Selected work
Furniture manufacturing ERP
A furniture production system that carries Kaspi orders through assembly and delivery. Managers, assemblers, and couriers work with the same orders, each with the access they need.
The estimate depends on the pages, workflows, integrations, and existing materials. Send your goal and examples; we clarify the scope before agreeing on a budget. Hosting and third-party service costs are discussed separately.
We break the work into milestones after reviewing the scope and dependencies. If you have a launch date, share it at the start so we can discuss what fits.
Yes. Send a link and describe what is getting in the way. We first review the current system and access available, then decide what to change.
I review the task and ask about users, current tools, and the intended result. We then decide whether the next step is an estimate, a review of the existing product, or a more detailed brief.
We agree on source code, account access, documentation, and ownership terms before development. Any third-party licenses and services are identified as part of the scope.
We agree on handover and any ongoing support before launch, including responsibilities and costs. Hosting, maintenance, and future features are separate items to discuss.
Send your goal, a link or example, and your preferred timing. I’ll review the task and ask what is needed to estimate the work.