# Less searching. More doing. Ask across your records, then turn the answer into a working system. You decide what ships. [Get started](https://console.path.dev/signup)[Talk to us](https://path.dev/contact-sales) [See Scout in action](https://path.dev/platform/scout#scout-in-action) One conversation. A working app.Built with Scout ←→ app.path.dev/apps/northstar-studio/edit Northstar Studio · Edit ![](/path-mark-ink.png)Northstar Studio Build a booking app for our studio. Keep customers, availability, and follow-ups together. ![](/path-mark-ink.png) Scout Your booking workspace is ready to preview. * Customer and booking records * Availability and scheduling * A daily view for your team Checkpoint · Booking workspace What should we improve next? Northstar StudioDesktopPreview**Publish** Northstar StudioBookings Your day, organized Good morning, Alex. Bookings today**12** Need a follow-up**3** Available spaces**4** **Upcoming bookings**Today AL **Alex Lee**Studio session 9:00 AMConfirmed JM **Jordan Miller**Team workshop 11:30 AMFollow up SP **Sam Patel**Consultation 2:00 PMConfirmed Customers, availability, and bookings. Connected. Path App editor · Example data ## From a question to a working system. Your context, without the catch-up. Your ideas, with an AI engineer to help make them real. 01 / 04 Understand ### Start with your business. Bring records, documents, and connected tools into the conversation. Ask Scout to find context and shape the next step. [Explore integrations](https://path.dev/platform/connectors) BookingsStudio handbookConnected tools Which bookings need a follow-up? ![](/path-mark-ink.png)Scout Start with these three. Team workshop**Confirm attendee count** Private session**Send the booking details** Studio rental**Review the requested time** Context: booking records and studio handbook Your records. Your process. A useful next step. Path platform interface · Example data 02 / 04 Build ### Make the missing piece. Describe the workflow you need. Build the screens, data, and logic with Scout, then explore the working preview. [Explore Apps](https://path.dev/platform/apps) ←→ app.path.dev/apps/northstar-studio/edit Northstar Studio · Edit ![](/path-mark-ink.png)Northstar Studio Build a booking app for our studio. Keep customers, availability, and follow-ups together. ![](/path-mark-ink.png) Scout Your booking workspace is ready to preview. * Customer and booking records * Availability and scheduling * A daily view for your team Checkpoint · Booking workspace What should we improve next? Northstar StudioDesktopPreview**Publish** Northstar StudioBookings Your day, organized Good morning, Alex. Bookings today**12** Need a follow-up**3** Available spaces**4** **Upcoming bookings**Today AL **Alex Lee**Studio session 9:00 AMConfirmed JM **Jordan Miller**Team workshop 11:30 AMFollow up SP **Sam Patel**Consultation 2:00 PMConfirmed Customers, availability, and bookings. Connected. Path platform interface · Example data 03 / 04 Refine ### Good ideas get better. Ask for a change, inspect the result, and test it together. Keep refining until it works the way you do. [Read the Scout guide](https://path.dev/guides/features/scout) ![](/path-mark-cream.png) “Let customers review the details before confirming.” Preview your changeBooking flow New confirmation step Does everything look right? Session Team workshop Time Thursday, 11:30 AM Attendees 8 people Confirm booking Review the flowTest the changeKeep a checkpoint Path platform interface · Example data 04 / 04 Run ### Put it into everyday use. Review and publish your app on Path. Keep improving it with Scout as your business changes. [Explore publishing](https://path.dev/platform/deployments) From your preview to your team 1 Review 2 Preview 3 Publish bookings.example.comPublished Northstar StudioBookings Your day, organized Good morning, Alex. Bookings today**12** Need a follow-up**3** Available spaces**4** **Upcoming bookings**Today AL **Alex Lee**Studio session 9:00 AMConfirmed JM **Jordan Miller**Team workshop 11:30 AMFollow up SP **Sam Patel**Consultation 2:00 PMConfirmed Customers, availability, and bookings. Connected. Built with Scout. Published when you decide. Path platform interface · Example data Understand01 / 04 BookingsStudio handbookConnected tools Which bookings need a follow-up? ![](/path-mark-ink.png)Scout Start with these three. Team workshop**Confirm attendee count** Private session**Send the booking details** Studio rental**Review the requested time** Context: booking records and studio handbook Your records. Your process. A useful next step. Path platform interface · Example data ## Your judgment. Scout’s engineering. ### Shape the plan Start with an outcome. Share the context and agree on what the system should do. ### Review the work Inspect the changes, try the preview, and ask Scout to test and refine the result. ### Decide what ships Build on Path’s data, access controls, and infrastructure. Publish when you are ready. [A guide to working with Scout](https://path.dev/guides/features/scout) ## Start somewhere useful. [ ### Company operations Approvals, reporting, and the work that used to live in your inbox. ](https://path.dev/systems/operations)[ ### Property operations Leasing, maintenance, and site reporting, connected to the people doing the work. ](https://path.dev/solutions/industries/real-estate)[ ### Customer portals Give clients, tenants, and partners a place to get things done. ](https://path.dev/platform/portals)[ ### Decision support Research, comparisons, and next steps grounded in your business context. ](https://path.dev/guides/features/scout) ## Start with one question Find the answer, decide what matters, and put it to work. [Get started](https://console.path.dev/signup)[Talk to us](https://path.dev/contact-sales) Source: https://path.dev/platform/scout