RU Book a demo
Book a demo
Sign in Русский

    Try

    Sales, the shop floor and the family budget — built from the same parts

    Every scenario on this page is assembled in Eyeward from modules, relations, views and rules. Each one comes with a drawing of its modules, the views and documents it relies on, and a path to set it up.

    There is no ready-made “CRM” or “manufacturing system” inside the platform. There are parts that teams assemble around their own process — or install as a copy from the Solutions store.

    Book a demo Build your own

    A sale moves through a chain of records — from inquiry to payment

    This is how one company set up sales in Eyeward: eight modules, the relations between them, automatic statuses and documents. There is no built-in CRM — you assemble a pipeline like this yourself, or install a copy from the Solutions store once someone publishes one.

    View A — sales modules and how they connect An arrow is a parent → child relation. The label on it is the button that creates the record. Dashed lines lead to a document and to the next scenario.

    One sale, step by step

    Order ЗАК-0042 “Pumping station NS-40” from opportunity to first payment.

    1. Step 1 Opportunity

      Opportunity Open

      Pumping station NS-40 · Talver-Agro

      Sales stage
      Needs analysis
      Probability
      40%
      Expected close date
      Aug 31, 2026
      You click
      Client card → “…” menu → “Create opportunity”
      On its own
      The date, the “Open” status and the “Existing client” source are filled in automatically.

    2. Step 2 Quotation

      Quotation Open

      Pumping station NS-40 · Talver-Agro

      Line items
      3 lines: pumps, directional valves, hoses
      Subtotal
      128,400.00 Br
      Total with 20% VAT
      154,080.00 Br
      You click
      Opportunity → “…” → “Create quotation”
      On its own
      The counterparty and the owner carry over. The opportunity switches to “Quotation” on its own.

    3. Step 3 Quote in Word

      Document · DOCX

      Pumping station NS-40 · Talver-Agro

      Template
      “Commercial offer”
      Inside
      line items in a loop, company details and logo
      Total
      the amount in words (in Russian)
      You click
      The “Document” button on the quotation card
      On its own
      A .docx file is generated from the record. Print it from Word or LibreOffice — there is no PDF export.

    4. Step 4 Deal

      Deal · ЗАК-0042 To production

      Pumping station NS-40 · Talver-Agro

      Line items, VAT, payment schedule
      copied from the quotation
      Shipping date
      Sep 18, 2026
      Quotation status
      “Ordered”
      You click
      Quotation → “…” → “Create deal”
      On its own
      The quotation becomes “Ordered” because the deal covers its total. The deal is “To production” because it has line items.

    5. Step 5 To the shop floor

      Deal · ЗАК-0042 To production Orders created

      Pumping station NS-40 · Talver-Agro

      Work orders
      3 — one per line item
      Next
      production drives the status up to “Produced”
      You click
      Deal → “…” → “Create work orders”
      On its own
      Each work order gets the item, quantity and due date. The deal status changes on its own.
      What happens on the shop floor

    6. Step 6 Payment

      Deal · ЗАК-0042 Payment status: Unpaid Partially paid

      Pumping station NS-40 · Talver-Agro

      Payment received
      77,040.00 Br — 50% prepayment
      Paid
      77,040.00 Br
      Balance due
      77,040.00 Br
      You click
      Deal → “…” → “Record payment”
      On its own
      The deal recalculates “Paid” and “Balance due”, and the payment status changes on its own.
    ItemModuleWhat the record holdsWhere it comes from
    1LeadFirst contact: details, source, statusEntered by hand or imported from Excel. There is no button that turns it into a client — the opportunity links them
    2ClientTax ID, client type, ownerEntered by hand; the form adapts to the client type and country
    3ContactA person at the client: position, phone, emailThe “Create contact” button; shown as tiles on the client card via a Record card field
    4RequisitesBank accounts, signatories, directorThe “Create requisites” button; five fields stay in sync with the client both ways
    5OpportunitySales stage, probability, expected amountThe “Create opportunity” button on the client; a lead can be the counterparty too
    6QuotationLine items, VAT, total, payment schedule, signatoryThe “Create quotation” button; can also start without an opportunity
    7DealLine items, shipping date, production and payment statusesThe “Create deal” button — or created directly for a client
    8PaymentsAmount, date, payment method, split across line itemsThe “Record payment” button on the deal

    How to build a pipeline like this

    7 setup steps
    1. Create the Client, Opportunity, Quotation, Deal and Payments modules. Drag fields onto the form; line items and the payment schedule are table fields.
    2. On each child module’s Relations tab, pick its parent. Make “Counterparty type” and “Counterparty” a relation group so an opportunity can belong to a lead or a client.
    3. On the Statuses tab, set the steps and the transitions: “when a related record is created” and by the sum of child records.
    4. On the Actions tab, build the “Create quotation”, “Create deal” and “Record payment” buttons and choose which fields they copy.
    5. In Documents, build the quote template: line items in a loop, company details, the amount in words.
    6. Add a Kanban of opportunities by stage and a “CRM” workspace with a funnel.
    7. Set up roles: sales managers see only their own records.

    An order moves through the shop by its BOM — and shows up on a Gantt chart by shop

    The manufacturing pipeline runs on general-purpose platform mechanics: table fields, actions, status transitions and the Gantt chart. There is nothing machine-specific in the platform itself — BOMs, work orders and job cards are modules just like clients and deals.

    Take the drawing apart by module

    Pick a module — the drawing keeps only it, its links and its neighbors.

    View B — from a deal line item to an operation on the shop floor An arrow is a parent → child relation; its label is an action button or the role of the link. Dashed lines are not relations but effects: a view of the records and the “Waiting for material” status.
    Photo of a hydraulic equipment shop: a welding bay in the foreground with a pump station frame on the table, a welder in a mask at work, and further back lathes and a worker at a machine, seen from behind.
    View B1 — the welding bay, where the job cards for ЗАК-0042 get closed

    Click a bar to open its record below. Drag the bar with the mouse, as in the app; the ← → keys on a bar and the buttons in the record do the same from a keyboard or a phone.Tap a bar to open its record below. Drag the selected bar with your finger, as in the app; the buttons in the record move it by a day.

    Production Gantt chart
    Shop

    Machining

    Welding

    Paint shop

    Assembly

    ЗАК-0042 In production

    Pumping station NS-40

    Client
    Talver-Agro
    Shop
    Welding
    Planned start
    Aug 17, 2026
    Planned finish
    Sep 11, 2026
    Duration
    26 days
    Delivery date
    Sep 18, 2026
    Amount
    128,400.00 Br

    No changes yet. Moving a bar edits two fields of the record: both dates shift by the same amount, the duration stays.

    The other bars stay put: the Gantt chart doesn’t reschedule anything by itself.

    View C — Gantt chart: orders by shop
    Status colors and the dimension line

    Bar color is the order status. The dimension line measures how much slack the selected order has before its delivery date: ЗАК-0042 finishes welding a week early.

    • In production
    • Confirmed
    • Shipped
    • Ready to ship
    • Draft
    ItemModuleWhat the record holdsWhere it comes from
    1DealLine items, shipping date, eight automatic statusesFrom sales — or entered by hand
    2Work orderItem, quantity, due date, the chosen BOMThe “Create work orders” button: one per line item. Running it again updates the orders instead of duplicating them
    3BOMOperations by work center, stages, setup time, materials with consumption ratesAn engineer sets it up once per product; the work order shows a read-only copy
    4Job cardOperation, stage, actual time log, ten automatic statusesThe “Create job cards” button on the work order: one card per operation
    5EquipmentMachines, working hours, queue and urgencyA reference list; the Resource planner fits work into free machine time
    6InventoryItems and movements: on hand, reserved, availableThe “Reserve materials” button on the work order; a shortage switches job cards to “Waiting for material”

    How to build a pipeline like this

    6 setup steps
    1. A “BOM” module with an “Operations” table field: work center, operation, time, output per run. A “Row dependencies” column groups operations into stages.
    2. “Work orders” is a child module of “Deal”: a relation field to the BOM, operations copied from it.
    3. On “Deal”, a “Create records from line items” action: one work order per line.
    4. “Job cards” — the same kind of action on the work order, one card per operation. The time log is a table field; statuses are transitions driven by the log.
    5. A Gantt chart view: lanes by shop or by order, “Work log”, “Stages and gates”.
    6. When you need them — “Equipment” with the planner, and inventory with material reservations.

    Inventory and shifts run on the same mechanics

    Stock levels and work schedules are modules and actions too, not separate programs. Both pipelines are described in the Eyeward knowledge base and are assembled around your own routine.

    Inventory: stock is calculated from movements

    Stock is never a number someone types in. “On hand”, “Reserved” and “Available” are rebuilt from movements — so correcting stock means posting a movement.

    View D — inventory and reservations for production

    Available = On hand − Reserved

    Movement buttons, reserves and what’s missing
    • Receipts, issues and reservations are buttons on the item card; a transfer is a pair of movements with “Create matching receipt”.
    • A reservation for a work order calculates the shortage; job cards of a stage without material switch to “Waiting for material”.
    • Not there: batches and FIFO, writing off reservations as production happens, linking a deal’s shipment to stock.

    Shifts: a two-on, two-off cycle unrolls into records

    The platform has no notion of a “shift”. There is a “Work patterns” record with a table field — one row per day of the cycle — and a “Create records on a cycle” action. It lays the cycle over the calendar and creates “Staff schedule” records for working steps only.

    Work patterns · “two on, two off”

    StepStartHoursType
    108:0012Day
    208:0012Day
    3——Off
    4——Off

    “Create records on a cycle” action · period Oct 5 — Oct 18

    Staff schedule

    Mo05Tu06We07Th08Fr09Sa10Su11Mo12Tu13We14Th15Fr16Sa17Su18
    Crew A DDDDDDDD 8 records
    Crew B DDDDDD 6 records

    D is a day shift, 08:00–20:00, and a record was created; empty means a day off, no record.

    Modes, crews and re-runs
    • Three modes: “Sequence of steps”, “By weekday” and “Auto”.
    • Crew B is a copy of the record with its first day moved by two: same cycle.
    • Running it again won’t duplicate shifts; one run creates up to 1,000 records.
    • The same action builds a maintenance plan “every 3 days” or a payment schedule.

    For yourself — the same modules, kept private

    A module outside a company is visible only to its author. There are no ready-made “personal” templates in the product: below are ideas for building your own from the same parts.

    Photo of a kitchen table during a renovation: a hand-drawn floor plan, a tape measure, paint swatches, receipts and an open laptop with a task list. Daylight, no people.
    View D — a renovation on the kitchen table: rooms, jobs, purchases
    Drawing — family budget

    Family budget: where the money goes

    Expenses by category with limits, savings goals and charts in your own workspace.

    What it is made of · Where to start

    What it is made of

    Fields
    Currency for amounts, a Rollup for what each category has spent, Progress for how much is saved toward a goal.
    Views
    An expense list with saved filters. A month filter is the condition “Date contains 2026-09”.
    Charts
    A Pie chart by category and a Line chart by month — as blocks in your own workspace.
    At hand
    Exchange rates and conversions right in the search bar: Bank of Russia, National Bank of Belarus or ECB.

    Where to start

    1. A “Categories” module with a “Limit” field and a child “Expenses” module: date, amount, category, a “Recurring” checkbox.
    2. In a category, add a Rollup field: the sum of its expenses. Set the Currency field symbol to Br — it defaults to ₽.
    3. Build the charts and place them in your own workspace — that becomes your budget dashboard.
    Drawing — renovation

    Renovation: tasks on a Gantt chart, estimates in files

    Rooms, tasks with dates and purchases. Every task has a Files tab for estimates, photos and drawings.

    What it is made of · Where to start

    What it is made of

    Fields
    The estimate is a table field and a formula totals each row; Progress is calculated from the table rows.
    Views
    A Gantt chart with your country’s public holidays and working days; a Kanban of tasks by status.
    Files
    “Before” and “after” photos, estimates, drawings. PDFs and 3D models open without downloading.
    Documents
    An estimate in Excel for a single task.

    You can draw dependencies between tasks, but the Gantt chart won’t reschedule them for you.

    Where to start

    1. “Rooms” → “Tasks” → “Purchases”: parent → child relations.
    2. Give “Tasks” start and end dates and a Gantt chart view; add your country’s holidays to the calendar.
    3. The estimate is a table field plus an Excel template with the “Single record” scope.
    Drawing — studies

    Studies: courses, notes and recorded lectures

    Courses and classes. Notes live in the record’s Notes tab, lectures in its files, deadlines are assignments to yourself.

    What it is made of · Where to start

    What it is made of

    Record tabs
    Notes in Markdown with pinning, and Files. Notes are off by default — turn them on in the module settings.
    Media player
    Speed from 0.25× to 2×, subtitles from .srt and .vtt files next to the video, resume where you stopped.
    Assignments
    To yourself, with a due date, priority and reminder; see them under Assignments → “To me”.
    Views
    A Kanban of classes by status: “Not started”, “Notes done”, “Reviewed”.

    Where to start

    1. A “Courses” module and a child “Classes” module: course, date, topic, status.
    2. On the General tab of “Classes”, turn on Notes and Files.
    3. A deadline is an assignment to yourself on a class: due date, priority, reminder.
    Drawing — a collection

    A collection: every piece is a record with a photo

    Pieces with a photo, rating and condition, series with a rollup, and an inventory list for insurance — in Excel.

    What it is made of · Where to start

    What it is made of

    Fields
    Image, Rating, a Select for condition, Currency for the purchase price. Tags live in the record sidebar.
    Views
    A list with counters and tags; a Kanban “Wanted → Owned → For trade”.
    Search
    Ctrl+K finds a piece by any field marked for search. Semantic mode finds it from a description in your own words, if it is enabled on your installation.
    Documents
    An inventory list in Excel from the current list selection.

    Where to start

    1. An “Items” module: image, year, condition, rating. Mark the fields you need as searchable in global search.
    2. “Series” as the parent module with a Rollup field: the number of pieces.
    3. An Excel template with the “List of records” scope — an inventory of the current selection.
    Drawing — travel

    Travel: bookings, a day-by-day route and a budget

    A trip, its bookings and the days of the route. Tickets live in the Files tab; exchange rates are right in the search bar.

    What it is made of · Where to start

    What it is made of

    Fields
    Currency takes its symbol from a currency-code field — bookings in euros, zlotys or roubles. A Rollup adds up the spending, Progress tracks the packing list.
    Views
    A Gantt chart with bookings and route days on one timeline; a Kanban of trips “Idea → Booked → Done”.
    At hand
    The rate on a given date and conversions right in the search bar.
    Files
    Tickets and bookings in the Files tab: PDFs open right in the browser.

    Where to start

    1. A “Trips” module with child “Bookings” and “Days” modules.
    2. In “Bookings”, add a currency-code field; the “Cost” symbol comes from it.
    3. In a trip, a “Packing list” table with checkboxes and a Progress field over its rows.

    Build your own — or install one that’s ready

    Every scenario above is built the same way: from the same eight layers, top to bottom. You can walk through them with the mouse — or describe your business to the assistant in Constructor mode: it assembles the same layers as a project and you press Deploy. Neither path needs an implementer.

    By hand: from a module to a dashboard

    1. Module and fields 34 field types in the palette; the form is assembled by drag and drop.
    2. Relations Parent → child; inherited fields as a copy, a shared reference or a live value.
    3. Statuses and rules “If… then…” rules, transitions on save and when a related record is created.
    4. Actions Buttons that create records in other modules.
    Steps 5–8: views, documents and charts, roles, workspace
    1. Views List, Kanban and Gantt chart — as many as you need, each with its own name.
    2. Documents and charts Word and Excel templates, 37 chart types.
    3. Roles Who sees and changes what — down to individual fields.
    4. Workspace A dashboard with number cards, charts and module shortcuts.

    Schema changes collect in a draft and apply with a single Save. You can roll a module back to any earlier version of its settings.

    Ready-made: from the Solutions store

    The Solutions store lives under System → Solutions store: some people publish their modules, others install them.

    WhatHow it works
    ContentsWhole modules: fields, form, rules, statuses and transitions, actions, ID generation. Plus relations, component lists, documents, views and demo records — up to 50 per module.
    ReviewA solution can’t be submitted while it references modules outside the package. A moderator reviews it before it goes live.
    Install“Just me” or into a company you own. You get an independent copy: the author can’t change it.
    ResetLinks to the author’s people, roles, companies, charts and files.
    UpdatesA new version installs next to the old one — there are no in-place updates. “Delete installed” removes the modules together with their records.
    PriceEverything in the store is free.

    The catalog is only starting to fill up. A scenario is often quicker to build yourself — and once it’s built, you can publish it for others.

    Let’s map your process in a demo

    Tell us how your sales, shop floor, inventory or anything else works — and we’ll show which modules, relations and views it takes in Eyeward.

    Book a demo Everything the platform does