Proven examples of what to tell the AI in NET Genium
The hardest part of the first application is not building it but describing it. This page gives you ready-made descriptions for the six agendas people most often start with in NET Genium — we ran each of them on a real instance and say what came out of it. Copy it, adapt it to your own company and send it.
There are two kinds of examples, because there are two ways into the AI in NET Genium:
- A description for the built-in generator — on the home page of your instance, in admin mode, you enter the name of the application and a description in your own words; from that single description the first version of the application is built: edit forms, the database tables behind them and view pages with the records. How the generator works is described on the page NET Genium AI.
- Prompts for a connected agent — Claude, ChatGPT or Microsoft Copilot Studio connected to your instance through the integrated MCP server builds the application, keeps developing it and works with its data every day. The connection takes a few minutes, following the guide Connecting an AI tool to the MCP server.
Both routes lead to the same place and can be combined: you let the generator build the application, and the agent then extends it and works in it with the data.
How to use the examples
- Write about your company, not about software. The descriptions that work best explain how the process runs at your company: who creates what, what is recorded and which statuses a record goes through. You do not have to name tables or data types — the AI proposes them.
- The generator asks for two things: the name of the application and a description. Put the name from the example into the field “Enter the application name”, the description into “Enter a description of your new application”, press “Create application” and answer whether you want sample data as well — with it you can click through the finished application straight away. The generator builds the forms, the relations between them and the sums, plus one view page with a list of records for each main form; filtered overviews, buttons with scripts and boards are added by the agent.
- The agent gets the prompt in the conversation. Before writing anything it shows you what it is about to create or change and you approve the proposal; each example therefore says what exists once you agree.
- Rewrite the names of statuses, categories and roles to match your own — the AI takes them literally. The actual result may differ slightly from the description below, because the AI proposes the structure; the sentences “What is created” describe what came out in our verification.
Orders and enquiries
Description for the generator
Application name: Orders and enquiries
We keep track of enquiries from customers and of the orders that come out of them. An enquiry has a customer, a contact person, the date received, a description of the request, an estimated price and a status: new, in negotiation, won, lost. Each enquiry is handled by one salesperson from our team. A won enquiry becomes an order with a number, a name, a delivery date, a responsible person and a status: entered, in progress, completed, invoiced. An order consists of items – each item has a name, a quantity, a unit, a unit price and a total price. On the order we want to see the sum of all item prices. We also keep notes from meetings and attachments on the order, for example the quotation as a PDF.
What is created: the forms Customer, Contact person, Enquiry, Order, Note and Attachment; the order items are a nested table right in the order form and their prices are summed automatically, the salesperson and the responsible person are chosen from the users of the instance. Each form gets a view page with a list of records and a button for a new record.
Prompts for the agent
- Build: “Build an application called Orders and enquiries in my instance: we track enquiries from customers (customer, contact, date received, description, estimated price, status new / in negotiation / won / lost, salesperson) and the orders that come out of them (number, name, delivery date, responsible person, status entered / in progress / completed / invoiced). An order has nested items with a name, quantity, unit and price, and a sum of the item prices. Propose the structure first, then write it.” — The agent reads the model of the instance, proposes the forms and their controls and, once approved, creates them through the MCP server together with the view pages.
- Extend: “Add the fields Handed over to customer (a date) and Complaint (a checkbox) to the Order form. Show both in the order overview and add a view page Overdue orders that lists unfinished orders whose delivery date is in the past.” — The agent adds both fields to the existing form, puts them among the columns of the overview and creates a new view page with query conditions.
- Daily work: “How many enquiries have we received this year, how many of them did we win, and what is the total value of the orders in progress? List the five orders with the nearest delivery date as well.” — The agent reads the records straight from the database of the instance and answers from them; nothing is changed.
Leave and expense approvals
Description for the generator
Application name: Leave and expense approvals
Employees submit leave requests and expense claims, and their manager approves them. A leave request has an applicant, a date from, a date to, a number of days, a type (holiday, sick day, unpaid leave, home office), a reason and a status: submitted, approved, rejected. An expense claim has an applicant, a date, an amount, a currency, a category (travel, accommodation, meals, equipment purchase, other), a description, the scanned receipt as an attachment and the same statuses. For both kinds of request we record who approved or rejected it and when, and the approver's note.
What is created: the forms Leave request and Expense claim — the applicant and the approver are chosen from the users of the instance, type, currency and category are drop-down lists, the status is a radio button and the receipt an attachment. Each form gets a view page with a list of requests and a button for a new request.
Prompts for the agent
- Build: “Create an application for leave and expense approvals: a leave request (applicant, from, to, number of days, type holiday / sick day / unpaid leave / home office, reason, status submitted / approved / rejected, who decided and when, note) and an expense claim (applicant, date, amount, currency, category, description, receipt as an attachment, the same statuses). Add a view page Pending requests where the approver sees the submitted requests of both kinds.” — The agent creates both forms and three view pages; it proposes the status and category as select controls with the values from the prompt.
- Extend: “Add Approve and Reject buttons to both forms. They should set the status, fill in the signed-in user and today's date in the decision fields and save the record. Show the buttons only on a submitted request.” — The agent adds the buttons with scripts that set the values and save the record, and a form JavaScript that hides the buttons on a request that has been decided.
- Daily work: “List all submitted leave requests and expense claims and, for each, give the applicant, the dates or the amount and how long it has been waiting for a decision.” — The agent reads the requests from the instance and composes the answer; nothing is changed.
Complaints and service
Description for the generator
Application name: Complaints and service
We receive complaints and service requests from customers. A complaint has a number, a customer, the date received, the product complained about, its serial number, a description of the fault, photos of the fault and a status: received, in progress, waiting for a part, resolved, rejected. Each complaint is handled by one technician, and we record how it was resolved (repair, replacement, refund, rejected) and the date of resolution. The technician records service interventions on the complaint – each intervention has a date, a description of the work done, the parts used, the number of hours and a price. On the complaint we want to see the total hours and the total price of the interventions.
What is created: the form Complaint with the nested table Service intervention; the hours and prices of the interventions are summed on the complaint automatically, the technician is chosen from the users of the instance and the customer from an existing customer list, if the instance has one (otherwise the AI creates a Customer form as well). The complaints get a view page with a list and a button for a new complaint.
Prompts for the agent
- Build: “Build an application called Complaints and service: a complaint (number, customer, date received, product, serial number, fault description, photos, status received / in progress / waiting for a part / resolved / rejected, technician, resolution, date of resolution) with nested service interventions (date, work done, parts, hours, price) and the sum of hours and price.” — The agent proposes the structure including the nested form and writes it once approved.
- Extend: “Add a view page Open complaints by technician — a statistics table with the number of unresolved complaints and the total hours for each technician — and a page Complaints waiting for a part sorted by the date received.” — The agent creates two view pages: one with an aggregate query grouped by technician, the other with a condition on the status.
- Daily work: “Which complaints have been in progress for more than 14 days and who is handling them? For the ones waiting for a part, list the fault description.” — The agent reads the complaints and interventions from the instance and answers; nothing is changed.
Stock and assets
Description for the generator
Application name: Stock and assets
We keep records of stock items and company assets. A stock item has a code, a name, a category, a unit of measure, a minimum stock level, the current quantity and a location in the warehouse. Stock movements are recorded as receipts and issues – each movement has a date, a type (receipt, issue), an item, a quantity, who made the movement and a note. An asset has an inventory number, a name, a category (computer, phone, furniture, vehicle, machine), the date of purchase, the purchase price, a responsible person, a location, a status (in use, under repair, disposed of) and a photo. For each asset we keep records of service and inspections with a date, a description and a price.
What is created: the forms Stock item, Stock movement and Asset together with category lists; service and inspections are nested tables in the asset form and their prices are summed, the current quantity of an item is calculated from the movements. The main forms and the category lists get view pages with lists and buttons for a new record.
Prompts for the agent
- Build: “Create an application called Stock and assets: stock items (code, name, category, unit, minimum level, quantity, location), stock movements (date, receipt / issue, item, quantity, who, note) and assets (inventory number, name, category, purchase date, price, responsible person, location, status, photo) with nested service and inspection records.” — The agent creates the forms, the relations between them and the view pages.
- Extend: “Add a field Next inspection date to the asset form and a view page Inspections in the next 30 days that lists the assets with an inspection between today and 30 days ahead, sorted by date.” — The agent adds the field and creates a page with a date condition relative to today.
- Daily work: “List the assets Jane Smith is responsible for, with their purchase price and status, and calculate the total value of the assets in use.” — The agent reads the records from the instance and answers; nothing is changed.
Tasks and projects
Description for the generator
Application name: Tasks and projects
We manage projects and tasks in our team. A project has a name, a customer, a project manager, a start date, a planned completion date, a budget, a description and a status: in preparation, running, on hold, completed. Each project consists of tasks – a task has a name, a description, an assignee, a priority (low, medium, high, critical), a due date, estimated hours, hours actually worked and a status: new, in progress, in review, done. Team members add comments to a task with a date and a text. On the project we want to see the sum of estimated and worked hours of all tasks.
What is created: the form Project with the nested table Task, and in each task the nested table Comment; the estimated and worked hours of the tasks are summed on the project automatically, the manager and the assignee are chosen from the users of the instance. The projects get a view page with a list and a button for a new project.
Prompts for the agent
- Build: “Build an application called Tasks and projects: a project (name, customer, manager, start, planned completion, budget, description, status in preparation / running / on hold / completed) with nested tasks (name, description, assignee, priority, due date, estimated hours, worked hours, status new / in progress / in review / done) and comments on a task. The project should sum the estimated and worked hours of its tasks. Add overviews of tasks by assignee, overdue tasks and running projects.” — The agent proposes the two-level nesting and the overviews and, once approved, creates three forms and four view pages.
- Extend: “Add a view page Board with a kanban of tasks by status and a calendar of task due dates. Add a field Completion date to the task, filled in with today's date when a task is saved in the status done.” — The agent creates a view page with the Kanban and Calendar controls over the existing tasks, adds the field and a before-save script that fills it in.
- Daily work: “Which tasks are not done, which of them are overdue, and how many hours are estimated for them? Sort them by priority.” — The agent reads the tasks from the instance and answers; nothing is changed.
Contracts and documents
Description for the generator
Application name: Contracts and documents
We keep track of contracts with partners and the related documents. A contract has a number, a name, a contracting party, a type (purchase, service, lease, framework, NDA, employment), the date of signature, valid from, valid to, a notice period in months, a value, a currency, a responsible person, a status (in preparation, for signature, valid, terminated, ended) and the signed contract as an attachment. A contract has amendments – each amendment has a number, the date of signature, a description of the change and an attachment. We also store related documents on the contract with a name, a type (quotation, purchase order, report, invoice, correspondence), a date and a file.
What is created: the forms Contracting party and Contract; amendments and documents are nested tables in the contract form, type, currency and status are select controls, the signed contract and the document files are attachments. The contracting parties and the contracts get view pages with lists and buttons for a new record.
Prompts for the agent
- Build: “Create an application called Contracts and documents: a contract (number, name, contracting party, type, date of signature, valid from / to, notice period in months, value, currency, responsible person, status in preparation / for signature / valid / terminated / ended, attachment) with nested amendments (number, date, description of the change, attachment) and documents (name, type, date, file). Add overviews of valid contracts and of contracts by contracting party.” — The agent proposes the structure and writes it into the instance once approved.
- Extend: “Add a view page Contracts expiring within 90 days — valid contracts whose validity ends between today and 90 days ahead, sorted by the end of validity, with a sum of their value.” — The agent creates a page with conditions on the status and the date range and with a totals row.
- Daily work: “Which contracts end by the end of the year, what is their value and who is responsible for them? Give the number of amendments for each.” — The agent reads the contracts and amendments from the instance and answers; nothing is changed.
Try it on your own agenda
Pick the example closest to what you keep in a spreadsheet today, rewrite it to match your company and paste it into your instance. With a single user the instance is free with no time limit, with no credit card and nothing to install — you invite colleagues when you are ready. What you get in the instance and what additional users cost is described on the page NET Genium Online.