Concept

What built with you means in Rose Rocket: setup is shared

Built with you means setting up Rose Rocket is shared work: the platform supplies the parts, your team arranges them, and Rose Rocket builds beside you.

Published September 22, 2026Verified on release 2026.9
Object BuilderBoard BuilderRocket EngineOrdersCustomersInvoicesBoardsCustom objects
Four chart panels an operation put together from its own orders, floated over a forest highway: Orders by cities as lines for Toronto, Vancouver and Calgary; Orders as percentage this month as a donut of Booked, In transit, Delivered and Problem; Top carriers this month as bars for SwiftHaul, NovaCargo, ArcticFreight, BlueRail Exp. and SummitLine; Carrier performance over the last three months as a radar chart
On this page3 sections
  1. What it is
  2. The parts the platform gives
  3. Who builds
  4. What changes after go-live
  5. Where you meet it in Rose Rocket
  6. Go deeper

What it is

Setting up Rose Rocket is a shared job: the platform gives the parts, your team puts them together, and Rose Rocket builds alongside you instead of handing over a finished product.

Take a carrier going live, for example a flatbed carrier moving steel and lumber. In its first weeks the team decides what its orders carry, a required equipment type and a tarping instruction beside the standard fields; what the dispatch desk sees each morning, a board of today’s loads sorted by pickup time; and its first rule, holding an invoice until the signed BOL is attached. The team names the fields, picks the columns and writes the rule, and Rose Rocket’s team sits in the same sessions, building the first pieces together.

The parts the platform gives

The platform arrives with the parts every carrier and broker needs, and each part is shaped, not fixed. An object is one kind of thing you track, for example Order or Customer. A field is one piece of information about it, for example the tarping instruction the carrier adds to its orders. A board lists the records of one object, and a view is a saved tab of that board with its own filter and columns, for example the dispatch desk’s tab of today’s loads. A workflow is one of your rules written where the system reads it, for example holding the invoice until the BOL is attached. Putting Rose Rocket together means arranging these parts for your operation; none arrives already decided for you.

Who builds

The building is usually done by the people who already run the desk, an operations manager or a senior dispatcher who knows how the company books, moves and bills, with Rose Rocket’s team working beside them on the first fields, boards and rules and again whenever something new comes up.

What changes after go-live

Nothing is handed over. The same people who put the first board and the first rule together keep shaping the system as the operation changes: a new customer wants a PO number on every order, so someone on the team adds the field; the billing desk wants its own tab, so someone saves a view. There is no ticket to a vendor and no wait for a release. Rose Rocket’s team is still there for the harder pieces, for example a rule that touches several objects.

Builders call the assembled result configuration; the shared way of getting there is what built with you means.

Where you meet it in Rose Rocket

  • Object Builder (Settings › Builders › Objects, then an object such as Order) → the object’s Available fields list, with a Custom pill on each field your team added → the fields your team chose, where it adds the next one; see Object Builder.
  • Configure on the Orders board (Operations › Orders) → Configure View with the view’s filter, sort, grouping and columns → a desk’s tab, put together by the desk; see Board views.
  • Workflows table (Settings › Builders › Rocket Engine) → a row per rule with its object, event, condition and action → the first rule and every rule since, written by your team; see Platform basics.

Go deeper

More on Orders, Customers, Invoices, Boards, Custom objects