We’re redesigning an internal operational planning system (TimberFlow) and are seeking an experienced backend-first Xano architect to define and build the core engine.
This is a structural redesign — not a lift-and-shift rebuild.
Scope includes:
• State-driven order lifecycle
• 3-day production scheduling
• Capacity validation
• Tooling & material logic
• Region-based delivery planning
• Multi-drop route optimisation (vehicle capacity & duration constraints)
We’re looking for someone who thinks in:
• Clean data models
• Backend-enforced business rules
• Atomic state transitions
• API-first architecture
Frontend will consume defined endpoints. Business logic must not live in the UI.
Initial architecture-focused engagement (contract basis), approx. 4–8 weeks depending on agreed scope, with potential for further phases.
If this aligns with how you approach system design, please message me with:
• Relevant Xano backend examples
• Your approach to state-driven architecture
• Availability and rate
Remote. UK/EU time zone preferred.
Discovering Direct IT Contract Opportunities for Contract Spy members.