Can I use it across multiple client projects?

Yes. Each project is its own independent app built from its own spec, and one account can hold multiple projects.

Can I match my client’s preferred language and database?

The back end supports multiple languages. See the supported languages & databases page for current coverage.

Can the client’s own engineers modify it after delivery?

Yes. What you export is ordinary source code — front end, back end, and database schema — as a full ZIP. It can be read, modified, tested, and deployed anywhere.

Do I have to rewrite code every time requirements change?

No. You edit the visual design spec (screens, data, flows) and regenerate the code. Since generation comes from the spec rather than overwriting hand-edited code, a requirement change doesn’t mean starting over.

Can I deliver a template as-is?

Templates are a starting point. The intended flow is to adjust the screens, data model, and workflows to your client’s requirements, then generate and deliver the code.

Deliver client projects with code they actually own

For developers, agencies, and freelancers building business apps for clients. d-bye generates code from a design spec — screens, data, and workflows. What you generate exports as a full ZIP of source code that runs on your client’s own infrastructure. Starting from a template means the first draft is already there.

The risk of delivering on a tool that won’t give you the code

Building a client’s business app on a no-code/low-code tool that keeps everything inside its own platform tends to cause problems after handoff.

No clean handoff

If the app only runs inside the tool, your client is effectively locked into that vendor the moment they want to switch providers or bring maintenance in-house.

Can’t answer requests for real code

When a client needs custom logic or wants their own engineers to modify the app directly, a platform’s constraints can block that — or force a full rebuild from scratch.

Hard to scope as a contractual deliverable

When the deliverable needs to be "source code," not "access to a tool," the choice of underlying platform becomes the blocker before the project even starts.

Client work, built on d-bye

d-bye keeps a business app’s design spec (the IR) as the single source of truth, and generates real code from it.

✓The output is a complete source tree: a React/TypeScript front end plus a back end and database schema. Export it as a ZIP and hand it straight to your client’s repo and infrastructure.
✓The back end supports multiple languages, so you can match whatever stack your client already runs (See supported languages & databases).
✓Start from a template — approval workflow, inventory, sales orders, contact management, project/cost management, or attendance — and show a working first draft faster than designing from a blank page.
✓The spec is edited visually, so requirement changes don’t mean rewriting code from scratch — you edit the spec and regenerate.
✓What you hand off is plain source your client can read, modify, test, and extend with their own engineers.

A typical workflow

Start from the closest-fitting template (approval workflow, inventory, sales orders, contact management, project management, attendance) — or design from scratch.
Adjust the screens, data model, and workflows in the GUI to match the client’s requirements.
Walk through the browser preview with your client to confirm it before writing any code.
Pick the back-end language and database that match your client’s stack, and generate the code.
Export the full source as a ZIP and deliver it into your client’s repository and infrastructure.

Start from a template

Each one ships with real sample data — try it live in your browser right now.

Project · Time · Cost Management

Modeled on services/agency work itself — project profitability, time entries, cost & bill rates.

Approval Workflow

Multi-step approval routed by organizational hierarchy.

Inventory Management

Stock, movements, purchase orders, and PDF reports.

Sales Order Management

Quote → order → shipped → completed slip-based workflow.

Contact Management

Customers, inquiries, and response history.

Attendance Tracker

Clock in/out and attendance aggregation.

FAQ

Can I use it across multiple client projects?: Yes. Each project is its own independent app built from its own spec, and one account can hold multiple projects.
Can I match my client’s preferred language and database?: The back end supports multiple languages. See the supported languages & databases page for current coverage.
Can the client’s own engineers modify it after delivery?: Yes. What you export is ordinary source code — front end, back end, and database schema — as a full ZIP. It can be read, modified, tested, and deployed anywhere.
Do I have to rewrite code every time requirements change?: No. You edit the visual design spec (screens, data, flows) and regenerate the code. Since generation comes from the spec rather than overwriting hand-edited code, a requirement change doesn’t mean starting over.
Can I deliver a template as-is?: Templates are a starting point. The intended flow is to adjust the screens, data model, and workflows to your client’s requirements, then generate and deliver the code.

Next step

→Try a template as a working preview in the free Sandbox
→Start from whichever template is closest to your client’s requirements
→Full download requires Personal or higher (design and preview are free, no credit card)

Try a template See pricing