Describe how your team works inbound leads and Netiva’s agent builds a web app that hands each one to an owner, times the first touch and shows conversion by source — with code you own.
Build a lead management dashboard for a 12-person B2B sales team. Store leads with company, contact, email, phone, source, campaign and owner, plus a stage: New, Working, Qualified, Demo booked, Proposal, Won or Lost. A public form creates New leads and saves the utm_source, utm_medium and utm_campaign values from the link. Hand each new lead to the next owner in its territory. Reps sign in and log touches with channel, direction and outcome. Show a queue of leads with no outbound touch yet sorted by minutes waiting, a funnel with conversion between stages, and lead, qualified and won counts per campaign.
A demo request arrives at 4:50 p.m. on Friday, lands in a shared inbox and sits there until Monday. By then the buyer has talked to someone else. Meanwhile marketing counts form fills in one spreadsheet, sales counts opportunities in another, and neither side can say which campaign produced last quarter’s wins. A lead dashboard built with Netiva gives every inquiry an owner, times how long it waited for a first touch and shows stage-by-stage conversion for each source, so both teams open the same numbers on Monday.
Every inquiry becomes a lead record the moment it arrives, carrying the campaign values from the link it came through, and the app hands it to the next owner in that territory instead of leaving it in a shared inbox.
The queue lists leads nobody has reached out to yet, oldest first, with the minutes each one has been waiting. The first call or email a rep logs against a lead stops its clock.
The funnel counts leads at each stage for the period you pick and works out how many moved on to the next one, then splits those numbers by source, campaign and owner so marketing sees what happens after the form fill.
Reps sign in and open their own queue, the manager opens the same dashboard with everyone on it, and a scheduled email puts the week’s counts in front of sales and marketing before the pipeline meeting.
Netiva keeps your records in built-in collections. Here’s a starting structure — the agent adapts it to your prompt, and you can change it any time.
One record per inquiry, from the form fill to Won or Lost.
Every attempt to reach a lead and what came of it.
The dated trail behind the funnel, conversion rates and lost reasons.
What marketing is running, with the spend behind each one.
Required field. Types are Netiva collection field types.
A typical first version. Ask the agent for more, or annotate the preview to change any of them.
Leads with no outbound touch yet, oldest first, showing minutes waiting and the owner, with a box to log the call or email without leaving the list.
Signed-in usersContact details, source and campaign, the stage history with dates and every touch logged against this lead, with the next step at the top.
Signed-in usersStage counts and conversion between stages for a date range, filtered by source, campaign, owner or territory.
Your teamMedian and slowest time to first touch by owner and by day, with the leads that went past your target listed underneath.
Your teamLeads, qualified and won counts for each campaign next to the spend recorded against it, with cost per qualified lead.
Your teamThe public form that creates the lead, keeping the campaign values from the link that brought the visitor in.
PublicTell the agent which stages a lead passes through, which sources you buy or earn and how territories are split. It drafts the collections and the first screens while you watch, with no coding on your side.
Say who owns which territory, in what order new leads are handed out and how long one may sit before the app emails a reminder. The agent wires those rules into the queue.
Enter a dozen real inquiries in the collection grid, submit the public form in the live preview and check that the funnel and response tiles add up. Annotate anything that reads wrong and the agent fixes it.
Publish in one click, invite reps to sign in and switch on the alert and digest emails. Every later change is checkpointed, so an experiment on the funnel screen is easy to roll back.
| Criterion | With Netiva | Traditional build |
|---|---|---|
| Lead routing | Each lead gets an owner in turn within its territory, with the time it was handed over recorded | A shared inbox where whoever reads the alert first decides whether to take the lead |
| Source reporting | Lead, qualified and won counts per campaign, taken from the records reps update every day | Figures copied from ad accounts into a monthly deck that sales quietly disputes |
| Getting started | Describe what you need in chat and watch it take shape in a live preview | Hire developers, or stitch together templates, plugins and a hosting plan |
| Content and data | Built-in collections with nine field types, bound straight to your pages | Set up and connect a separate database or CMS |
| Making changes | Ask the agent; every change is checkpointed and reversible | File a ticket, wait for a sprint, redeploy |
| Hosting and domain | Global hosting and automatic SSL; connect a custom domain from the Starter plan | Buy hosting, then install and renew SSL certificates yourself |
| Code ownership | Clean production code you own and can export | Locked into a template, plugin or agency setup |
Demo requests are split by region and handed to the next rep in line. The sales manager watches the queue during the day and the response times screen on Friday, when the pattern behind a slow week is easier to see.
Inquiries arrive from two paid directories and the company’s own form. The campaign report puts spend next to qualified and won counts, so the owner can tell which directory is worth renewing in the spring.
Badge scans are entered as event leads the week after the show. The stage history shows they take far longer to qualify than a demo request, so they get a slower follow-up rhythm instead of being written off as cold.
The clock starts when the lead reaches the app and stops at the first outbound touch someone logs. Leads typed in a day late look fast, and a call from a personal phone counts only once it is written down, so agree with the team what gets logged.
The form keeps the UTM values from the link that brought a visitor in, which covers your own pages. Ad spend is entered each month, or pulled from an ad platform’s API with your own key, and offline sources such as referrals are tagged by whoever adds the lead.
The dashboard records outreach rather than running it. Reps still dial from their phone or dialer and write from their own inbox. Netiva apps can send internal alerts and digests by email; they don’t send text messages.
Reps sign in and each queue can be limited to the leads assigned to that person, but apps Netiva builds don’t come with manager and rep roles. Lead records hold personal contact details, so keep to the fields your team works from.
Two timestamps do it. The lead’s first stage row is written when the inquiry arrives, and every call, email or message a rep logs carries the time it happened. The clock runs from the first to the earliest outbound touch, and the queue shows the minutes still running on leads nobody has worked. You set the target — five minutes for a demo request, a day for a content download.
Yes. The inquiry form on your published site writes straight into the Leads collection, so a submission becomes a New lead with its campaign values and enters the routing order. If inquiries come through a form service or an ad platform instead, the app can call that provider’s REST API with your own key, stored securely, and create the same records on a schedule.
Each person signs in with their own account, and the queue and lead list can be filtered to records where they are the owner, which covers the daily working view. Netiva doesn’t give the generated app a role system, though, so anyone signed in can open a screen they know the address of. Split the screens with that in mind before you publish.
No. It records outreach rather than performing it: reps dial from their phone or dialer and write the outcome on the lead, and a phone number can be a tap-to-call link on the queue screen. The app can send email, such as an alert when a lead has waited too long and the Monday digest, but Netiva apps don’t send text messages.
Each campaign record holds the spend for the period, entered by the marketing lead or pulled from an ad platform’s API with your own key. The campaign report counts the leads attached to that campaign, how many reached Qualified and how many were won, then divides spend by the qualified count. Sources with no spend, such as referrals, show counts only.
Yes. Netiva writes clean, framework-standard code you can read in the editor and export whenever you want, with no proprietary runtime, and your lead data stays in your collections. Every change the agent makes is checkpointed, so you can branch a new funnel screen, compare it with what you had and roll back if it doesn’t help.
Drafted with AI assistance from Netiva’s product pages and reviewed by the Netiva team. Example data models, screens and prompts are illustrative starting points, not customer projects.
Describe it in a sentence and watch Netiva’s agent build it. Free to start — no credit card required.