Competitor teardown · a-IDEA, ICAR-NAARM tenant · captured 12 Oct 2026

Accubate, end to end

a-IDEA runs its incubation on Accubate today, at about ₹3.5 lakh a year. This guide walks through the a-IDEA tenant screen by screen, in the order an incubator actually works: set up a programme, open a call, receive and evaluate applications, select startups, support them, track their progress and fund them. Each screen has a plain description, a use case and a worked example, so the team can see exactly what INQB Zone has to match or beat.

25Programmes

59Cohorts

7,081Applications

360Startups

6,252Users

31 Mar 2027Licence ends

Captured read-only from a live tenant: nothing was edited, submitted or sent, and write requests were blocked at the browser. Startup names, people's names, emails, phone numbers and startup logos are blurred. All examples in the notes are fictional.

The life cycle in Accubate

Accubate is organised around a chain: a Programme holds Cohorts, each Cohort runs through a Pipeline of stages, an application Form feeds the pipeline, and applicants who clear it become Startups in the portfolio. Click a stage to jump to its screens.

01Set up the programmeProgramme, cohorts, roles and site settings.
02Open a callApplication form and public apply link.
03Receive applicationsApplications land in a pipeline by cohort.
04Screen and evaluateRounds, evaluators and scorecards.
05Select and onboardPromote, reject, onboard into a startup pipeline.
06SupportMentoring, events, courses and library.
07MonitorProfiles, KPIs, IPRs, engagements.
08FundSchemes, nominations and disbursements.
09Communicate and resolveAnnouncements, surveys, grievances, reports.
10The founder's sideApply, track status, keep the profile, get support.

Programmes, cohorts and site setup

Setup is where a-IDEA's admins build the skeleton every other module hangs on: Site (a-IDEA NAARM-TBI) > Programme (a recurring brand such as AGRI UDAAN or KRISHIBOOT) > Cohort (one edition or intake, e.g. AGRI UDAAN 7.0) > Pipelines (normally two per cohort: '<cohort> Applications', a multi-round selection funnel, and '<cohort> Startups', the incubated portfolio) > Rounds (each with its own public or private link, dates, application form, evaluation form, emails, payment and e-signature) > Forms (built in a separate Form builder and reused). A field Mapping (under Tools) copies answers from the application rounds into the startup profile when an applicant is onboarded. Around this sit users and roles (with access scoped by a Site > Programme > Cohort checkbox tree), directory profiles (mentors, investors, evaluators, managers), 298 mail templates, site settings (identity, MFA, preferences, custom option lists, default forms, integrations), a site calendar and a usage page. It is the start of the life cycle: nothing can be applied to, evaluated or incubated until a programme, cohort, pipeline, round and form exist.

Configure site identity, preferences, taxonomies and integrations
Create programme (the recurring brand)
Create cohort (one edition/intake) with eligibility, focus areas, partners
Create Applications pipeline and its rounds
Build and attach application and evaluation forms
Configure round rules (public/private, dates, emails, auto-promote, payment, e-sign)
Assign people and access (programme managers, cohort managers, evaluators, mentors)
Create Startups pipeline and map application fields to the startup profile
Monitor from the Home dashboard and Site Usage

Use cases

Programme Manager / Administrator

Set up a new edition of an accelerator call

Open Setup > Cohorts > Create New under the existing programme
Fill About, Eligibility, Industry, Focus Area, Partners, Contact (and, ideally, Timeline)
Set cohort Settings: reply-to address and grievance assignee
Setup > Pipeline > Add New: '<cohort> Applications' (type Application); add Round 1 (Public, dates) and later private rounds
Setup > Form > Add New (or copy last year's form) and attach it in each round's Application tab; attach an evaluation form in the Evaluation tab
Switch on round rules: submission email, existing-application check, weighted evaluation, rejection/promotion emails
Create '<cohort> Startups' (type Startup), choose modules, onboarding mail
Tools > Mappings: map application questions to startup profile fields
Cohort > Users: add evaluators and cohort managers; scope access in Users > Access
Share Round 1's public link /ext/form/<pipeline>/1/apply

Example. a-IDEA opens fictional AGRI UDAAN 10.0: Round 1 public 1 Jun to 15 Jul, Round 2 private due diligence for 40, Round 3 private pitch day for 15, 12 selected startups onboarded into 'AGRI UDAAN 10.0 Startups'.

Administrator

Give a new juror access to one cohort only

Setup > Users > Add New (role Evaluator)
Open the user's Access, Evaluator tab
Tick only the target cohort in the Site > Programme > Cohort tree and submit
Alternatively add them from Cohort > Users > Evaluators > Add New

Example. A fictional food-technology professor is scoped to AGRI UDAAN 10.0 so she sees only those applications.

Programme Manager

Tighten evaluation for a pitch-day round

Open the Applications pipeline, select the pitch round
Evaluation tab: Add Evaluation Form, Allow Weighted Evaluation, Report Conflict Applications
Turn off Allow Evaluator To View Scores so jurors do not anchor on each other
Hide Fields From Evaluator for sensitive fields

Example. For the fictional AGRI UDAAN 10.0 final round, jurors score on a weighted rubric and must flag any startup they advise.

Administrator

Adapt the startup taxonomy

Setup > Site Settings > Custom Options > Startup
Create Custom Options for Stage of Startup or Legal Status
New lists replace the defaults in startup profiles and filters

Example. a-IDEA adds 'Farmer Producer Organisation' as a legal status so its FPO cohorts can be reported separately.

Super-admin / Director

Check licence, seats and storage before renewal

Setup > Site Settings > Accubate Settings: read Subscription End Date and days left
Setup > Site Usage > Resources: storage trend, storage by module, Organisation Users seat count
Login History and Download Logs for audit

Example. The director sees 169 days left, 64 GB stored and 24 of 24 staff seats used, and asks for a renewal quote.

Screens 29

Monitor/app/dashboards

Home dashboard (admin)

Landing page for an admin. A welcome line and a site banner, then counter tiles (25 Programs, 59 Cohorts, 7,081 Applications, 360 Startups, 1 Session, 0 Courses, 2 Surveys), a Programs widget showing one programme at a time with its cohorts and application/startup counts, a Startups chart with tabs (Domain wise, Registration Year, Onboarding Year, Is Women Led, Stage, Status) and an Applications chart (Page Visitors by pipeline, New Applications Trend). Right rail: Quick References (Site Calendar, Library), Tech Support contact (the vendor), Actions Required (25 open grievances) and Upcoming meetings.

On screen: Programs/Cohorts/Applications/Startups/Sessions/Courses/Surveys tiles, Programme widget: cohort, applications, startups, total, Domain-wise startups bar chart (data updated daily), Application page visits per pipeline line chart, Actions Required, Upcoming

Actions available: Change Program (programme picker in widget), View Program, View All (programmes, startups, applications), chart type switch (pie/bar/table), All Pipelines filter, View grievances

Use case. Programme head or admin opens it daily to see the size of the portfolio and whether a call is drawing traffic.

Example. During a fictional AGRI UDAAN 10.0 call, the PM picks the AGRI UDAAN programme in the widget and watches the page-visits line for the '10.0 Applications' pipeline rise after a social-media push.

Configure site/app/setup

Setup hub

A card index of all configuration, grouped by life-cycle stage, each card with a one-line purpose and a live count: People and access (Users 6,253, Groups 0, Directory 10 profiles); Programmes and delivery (Programs 25, Cohorts 59, Pipeline 87); Content and communication (Form 155, Mail 256 templates); Site administration (Site Settings 0 integrations, Partnership 0, Calendar 0 upcoming, Site Usage, Payments 0 accounts). Cards can be pinned (star) and a 'Recently visited' row shows the last opened items.

On screen: Pinned, Recently visited, card counts

Actions available: pin card (star), open any card

Use case. Admin's starting point for any configuration change.

Example. An admin preparing a new call pins 'Pipeline' and 'Form' so they are one click away for the next two weeks.

Create programme/app/setup/programs/list

Programs list

All 25 programmes as large image cards (banner, name, type badge, created date, cohorts / applications / startups counts). Every programme is typed 'Incubation', including a hackathon, a conference, an FPO CEO course and a 'sensitization' entry. Header shows 'Showing 1-25 of 25', '25 Owned', Filters and a search box.

On screen: programme name, type (all 'Incubation'), created on, Cohorts, Application(s), Startup(s)

Actions available: Create New, View/Edit, Delete, Filters, Search

Use case. Admin creates a programme once per recurring brand and reopens it for each new edition.

Example. a-IDEA's fictional new scheme 'AgriSeed Grant (fictional)' would be created here once, then get a new cohort every year.

Create programme/app/setup/programs/list/69/details

Programme detail: Details tab (AGRI UDAAN)

Programme record with banner image, name, last-edited and created dates, and tabs Details and Users. Details holds rich-text Objective, Target and About. The right rail lists the programme's 6 cohorts (AGRIUDAAN 5.0 to 9.0 and Cohort 2021) with View links, and Associated Partners (none added).

On screen: banner, Objective, Target, About, Cohorts list, Associated Partners

Actions available: Edit, Back, View (cohort), View All (6), Manage Partners

Use case. Holds the evergreen description of a programme that each cohort inherits context from.

Example. For the fictional AGRI UDAAN 10.0 edition, the PM only adds a new cohort; the programme's objective and NABARD-supported 'About' text stay as they are.

Assign people/app/setup/programs/list/69/users

Programme detail: Users tab

Lists Program Managers attached to the programme, with Add New. For AGRI UDAAN (and the other programmes checked: ABI, a-IDEA Incubation Startup Details, SIDBI Seed Fund) it shows 'Program Managers (0) - No Program Managers have access to this cohort' (note the copy says cohort on a programme page). Access is in practice granted per user from Users > Access instead.

On screen: Program Managers (count)

Actions available: Add New, Edit, Back

Use case. Intended for giving a programme manager access to all cohorts of a programme.

Example. A fictional new PM for AGRI UDAAN would be added here to see every AGRI UDAAN edition.

Create cohort/app/setup/cohorts/list

Cohorts list

All 59 cohorts as image cards (banner, cohort name, parent programme, created date, Pipeline(s), Application(s), Startup(s)). The page is about 6,700 px tall; there is no table view, status (open/closed) or call dates on the card.

On screen: cohort name, parent programme, created on, Pipeline(s), Application(s), Startup(s)

Actions available: Create New, View/Edit, Delete, Filters, Search

Use case. PM creates one cohort per edition or intake and returns to it to manage its pipelines and people.

Example. Cohort 'AGRI UDAAN 7.0' shows 2 pipelines, 257 applications and 17 startups.

Create cohort/app/setup/cohorts/list/1344/details

Cohort detail: Details tab (AGRI UDAAN 7.0)

Cohort record with banner and tabs Details, Settings, Users. Details: About (rich text including what the programme offers and staff contact lines, blurred), Eligibility (bullets), Industry and Focus Area (chips: Agricultural, AI, Ayurveda & Wellness, Food & Beverages, FoodTech, Green Technology, Mechanization, Post-Harvest, Precision Agriculture, Rural Innovations), Partners (sponsor logos with Remove), Contact (a staff member). Right rail: Program Details (parent + 257 Applications / 17 Startups), Pipelines (AGRI UDAAN 7.0 Startups, AGRI UDAAN 7.0 Applications), Timeline ('No Timeline Prepared yet...' on every cohort checked) and Associated Partners (none, although partner logos appear in the left column).

On screen: About, Eligibility, Industry, Focus Area, Partners, Contact, Pipelines, Timeline

Actions available: Edit, Add partner, Remove partner, Add contact, View pipeline, Add/Edit timeline, Manage Partners

Use case. PM describes one edition: who may apply, which sectors, who sponsors it and whom to contact.

Example. For a fictional AGRI UDAAN 10.0, the PM sets eligibility to 'scale-up agri-food startups with a validated product', picks focus areas Precision Agriculture and Post-Harvest, and adds a sponsoring bank's logo as partner.

Create cohort/app/setup/cohorts/list/1344/settings

Cohort detail: Settings tab

Cohort-level settings that every pipeline round inherits: Grievance Assignee(s), the mail template sent to the assignee, the mail template sent to the issue creator (all 'Not Added'), From Email Address (a vendor notification address) and Reply Email Address (an a-IDEA address), each with Edit.

On screen: Grievance Assignee(s), Assignee mail template, Issue-creator mail template, From Email Address, Reply Email Address

Actions available: Edit

Use case. Admin sets who handles complaints for this cohort and which reply-to address applicants see.

Example. For a fictional AGRI UDAAN 10.0, replies are routed to the accelerator team's shared inbox and grievances go to the cohort manager.

Assign people/app/setup/cohorts/list/1344/users

Cohort detail: Users tab

Five role sections for the cohort, each with Add New: Program Managers (0), Cohort Managers (0), Evaluators (17, shown as name/email cards, blurred), Mentors (0), Portfolio Managers (0).

On screen: Program Managers, Cohort Managers, Evaluators, Mentors, Portfolio Managers

Actions available: Add New (per role)

Use case. PM attaches the jury and support people to one edition.

Example. For a fictional AGRI UDAAN 10.0 the PM adds 15 external jury members as Evaluators and two staff as Cohort Managers.

Create Applications pipeline/app/setup/builder/pipelines/list/2353

Application pipeline editor: rounds and General tab

The 'AGRI UDAAN 7.0 Applications' pipeline. Header toggles: Active, Display Startup Name, Hide Status (hide promoted/rejected/onboarded from applicants), Hide Round (applicants see 'Form-1, Form-2' instead of round names). Left: round cards (Round 1 Public with link /ext/form/2353/1/apply, start 22 Aug 2024, end 16 Oct 2024, Closed; Round 2 Private, OTP email verification required, 30 Nov 2024 to 10 Jan 2025, Closed; Rounds 3 and 4 Private), each with a gear and a '+' to insert a round. Right: the selected round's tabs General, Application, Application Form Design, Evaluation, Mentoring, Payment, E-Signature, Settings. General has toggles Currently Active Round, Promotional Email, Rejection Email, Withdraw Email. The editor shows 'Saved' and autosaves.

On screen: Active, Display Startup Name, Hide Status, Hide Round, Round type Public/Private, public URL, Starts/Ends, no end date, Status

Actions available: Edit Title, Delete, add round (+), round settings (gear), edit link, date pickers, toggles

Use case. PM designs the selection funnel of one cohort: an open first round, then invite-only rounds for shortlisted applicants.

Example. Fictional AGRI UDAAN 10.0 Applications: Round 1 public (1 Jun to 15 Jul), Round 2 private due-diligence form for the top 40, Round 3 private pitch day for the top 15.

Configure round rules/app/setup/builder/pipelines/list/2353?section=Application

Round editor: Application tab

Round-level application rules, all toggles: Add Application (attach a form), Edit Application Access Mail, Allow AI Form Submission, Submission Email, Form Saved Email (draft), Submission SMS, Auto Onboard to Startup (push into a startup pipeline on submission), Application auto Promote, Existing Application Check (by same email or phone), Allow Edit After Submission. Application Form Design tab says 'Application form not available for this round' when no form is attached.

On screen: Add Application, Allow AI Form Submission, Submission Email/SMS, Auto Onboard to Startup, Application auto Promote, Existing Application Check, Allow Edit After Submission

Actions available: toggles

Use case. PM decides how applicants interact with each round.

Example. For the fictional Round 1 the PM turns on Submission Email and Existing Application Check so one startup cannot apply twice with the same email.

Configure round rules/app/setup/builder/pipelines/list/2353?section=Evaluation

Round editor: Evaluation tab

Sixteen evaluator rules per round: Add Evaluation Form, Application Scoring (auto-score from answers), Allow Weighted Evaluation, Report Conflict Applications, Allow Edit (own scores), Allow Promote, Allow Reject, Allow View Tags, Show Round Status, Show Round Form Status, Show Round Submission Date, Show Application Link, Hide Promoted Evaluations, Hide Rejected Evaluations, Hide Fields From Evaluator, Allow Evaluator To View Scores. Other tabs read: Mentoring (One Time Mentorings), Payment (Receive payment, Payment Success Email, Reminder Emails, Payment Request Email template, link expiry Dynamic/Static default 7 days), E-Signature (Enable E-Signature), Settings (read-only copy of cohort settings with a link to change them).

On screen: Add Evaluation Form, Application Scoring, Weighted Evaluation, Report Conflict, Allow Promote/Reject, Hide Fields From Evaluator, Allow Evaluator To View Scores

Actions available: toggles

Use case. PM sets how the jury scores a round and what they may see or decide.

Example. For the fictional pitch-day round the PM enables Weighted Evaluation and Report Conflict, and hides the applicant's funding history field from evaluators.

Create Applications pipeline/app/setup/builder/pipelines

Pipelines list

All 87 pipelines as cards with badges Active/Inactive, programme type (Incubation) and pipeline type (Application or Startup), the parent programme and cohort links, rounds count and applications or startups count. 56 are Application pipelines and 31 Startup pipelines; 80 active, 7 inactive.

On screen: pipeline name, Active/Inactive, type Application/Startup, programme, cohort, Round(s), Application(s)/Startup(s)

Actions available: Add New, Add filter, Search Pipelines, Clear all, View/Edit, Delete

Use case. Admin finds a cohort's funnel or portfolio pipeline to edit it.

Example. 'KRISHIBOOT 10.0 Applications' (1 round, 14 applications) sits next to 'KRISHIBOOT- 9.0 Startups' (5 startups).

Create Startups pipeline/app/setup/builder/pipelines/list/2960

Startup pipeline editor: Onboarding tab

The 'AGRI UDAAN 7.0 Startups' pipeline. Left panel switches modules on for incubated startups: Active, Documentation, Canvas Model, IPRs (Patents, Copyrights, Trademarks, Publications), Startup Connect (Market Access), Others (Awards, Documents, Portfolio Management). Tabs: Onboarding; Application, Portfolio & Company Profile; Documentation; Updates; Mentoring; Evaluation; Resource; Settings. Onboarding lists the source application pipeline (AGRI UDAAN 7.0 Applications), other startup pipelines (none), Direct Onboarding with its own URL (/ext/startup/apply/2960), User Onboarding Email (send login credentials), Onboarding Email with template 'Agri Udaan 7.0 - Onboarding' and CC list, Hide pipeline from Startups, Prompt Incomplete Profile on Dashboard, Incubation Completion Reminder (to managers before the expected graduation date).

On screen: module toggles, Onboarding through Applications, Direct Onboarding URL, Onboarding Email template, Incubation Completion Reminder

Actions available: Add (source pipeline), Change template, Add CC, toggles, Back

Use case. PM defines what an incubated startup of this cohort must maintain (IPR, documents, updates) and how selected applicants become startups.

Example. For the fictional AGRI UDAAN 10.0 Startups pipeline, selected applicants are onboarded from the Applications pipeline and get the onboarding mail; Patents and Awards are switched on, Canvas Model off.

Build forms/app/setup/builder/form

Forms list (Form builder)

Table of 164 forms (the Setup card says 155), 20 per page: Title, Last Modified, Category (Application or Startup), Label (REGULAR, UPDATES, PORTFOLIO), Created By (blurred), Status (PUBLISHED), Actions menu. Forms are named per round, e.g. 'Agri Udaan 6.0 - 1st Round Application', 'NABARD CCF Investment 3rd/Final Round', 'Expenditure incurred during the quarter' (startup update), 'BIRAC BIG PORTFOLIO'.

On screen: Title, Last Modified, Category, Label, Created By, Status

Actions available: Add New, Add filter, Search Form, View 20, Open options (per row), pagination

Use case. Admin builds a new form for each round, or a periodic update/portfolio form for startups.

Example. For the fictional AGRI UDAAN 10.0, the PM copies last year's '1st Round Application' form, edits the year in the title and attaches it to Round 1.

Build forms/app/setup/builder/form/2457

Form preview (Agri Udaan 6.0 - 1st Round Application)

Full-screen preview of a form with Save, Edit, Print and Close. This application form has 43 numbered questions: name, startup name, director expertise, email, phone, registered?, registered address, website, LinkedIn, women-led (51% shareholding), investment status, focus area (25 options), descriptions with character limits (1,000 to 4,000), technology use, competitive landscape, a co-founder grid (4 columns), and later uploads.

On screen: numbered questions, required marks, character counters, radio and checkbox options, grid questions

Actions available: Save, Edit, Print, Close

Use case. PM checks how applicants will see a form before attaching it to a round.

Example. A fictional startup 'AgroSense (fictional)' would see 43 questions, starting with founder name, startup name and contact details.

Configure communication/app/setup/builder/mail

Mail templates

Table of 298 mail templates (the Setup card says 256): Title, Last Modified, Created At, Category, Created By, Status, Actions. Categories seen: Mentoring, MentorRequest, Application, Funding, Payment, Grievance, Investment, Invoice, Announcement, Session, On-Boarding, Updates Reminder. System templates carry a lock icon and cannot be deleted; titles use merge tags such as {{Sid}}.

On screen: Title, Category, Created By, Status, lock icon

Actions available: Add New, Add filter, Search Mail, Edit, Duplicate, Delete (disabled for locked)

Use case. Admin writes the emails a round or pipeline sends (promotion, rejection, onboarding, payment reminder).

Example. For the fictional AGRI UDAAN 10.0, the PM duplicates 'Agri Udaan 7.0 - Onboarding' and renames it for 10.0.

Assign people/app/setup/access/user

Users and roles

User directory with a role filter showing counts: All Users 6,252, Applicant 5,883, Startup owner 281, Evaluator 216, Administrator 20, Program Manager 6, Course Manager 6, Mentor 3, Cohort Manager 2, Guest 2, Evaluation Manager 1, Funding Portfolio Manager 1, Fund Manager 1, Instructor 1, Portfolio Manager 1. Each user is a card (name, email, role chips, avatar; blurred) with Access, Edit, Delete. A banner offers 'go back to the older view'.

On screen: role filter with counts, role chips per user

Actions available: Add New, Refresh, Import, Search, Access, Edit, Delete

Use case. Admin creates staff and jury accounts and gives them roles.

Example. A fictional visiting expert is added as Evaluator and Mentor, then scoped to two cohorts through Access.

Assign people/app/setup/access/user (Access modal)

User access scope (modal)

Modal opened from a user's Access button. One tab per role the user holds (here Mentor, Cohort Manager, Evaluation Manager); under 'Select access level' a checkbox tree of Site > every programme > every cohort (all 25 programmes and 59 cohorts listed). In the example the Mentor role is scoped to one cohort (AGRI UDAAN 8.0).

On screen: role tabs, Site checkbox, programme checkboxes, cohort checkboxes

Actions available: Submit, Cancel, close (X)

Use case. Admin limits what each role of a user can see, per programme or cohort.

Example. A fictional cohort manager for AGRI UDAAN 10.0 gets only that cohort ticked under the Cohort Manager tab.

Assign people/app/setup/profiles/evaluators

Directory profiles: Evaluators

Directory of people profiles by type, tabs Mentors, Investors, Evaluators, Program Managers, Cohort Managers, Portfolio Managers, Evaluation Managers. Evaluators shows 216 results (name and email, blurred) with an Access button each. Counts read: Program Managers 6, Cohort Managers 2, Portfolio Managers 1, Evaluation Managers 1. The Mentors and Investors tabs did not render because their list calls are POST requests the read-only guard blocked.

On screen: profile type tabs, Name, Email, Actions

Actions available: Filters, Search, View 20, Access

Use case. PM looks up an existing evaluator or mentor before inviting a new one.

Example. Before adding jury for a fictional AGRI UDAAN 10.0, the PM searches the 216 evaluators for past jurors in post-harvest technology.

Configure site/app/setup/sites/item/platform

Site Settings: Accubate Settings

Site identity and contract: Site Id 'aideanaarm', Short Name 'a-IDEA NAARM-TBI', Full Name 'a-IDEA, NAARM-TBI', time zone Asia/Calcutta, a Multi-Factor Authentication toggle for all users (off), From and Reply email addresses, website and social links, and Subscription Details: start 22 Jul 2021, end 31 Mar 2027 10:00 AM, 169 days left (on 12 Oct 2026). Tabs: Accubate Settings, Default Forms & Backgrounds, About, Site Preferences, Custom Options, Static Data Setup, Integrations.

On screen: Site Id, Short/Full Name, Time zone, MFA for all users, From/Reply email, Social links, Subscription start/end, days left

Actions available: Edit, Contact support, MFA toggle

Use case. Super-admin sets the tenant identity and sees the licence term.

Example. The admin sees the Accubate subscription ends on 31 Mar 2027 and plans the renewal decision.

Configure site/app/setup/sites/item/preferences

Site Settings: Site Preferences

Language for new users (English (US)), Currency for new users (not selected; the preview formats ₹1,234,567.89 in Western grouping), Application Form Marketing ('auto-enable public listing of new application forms on accubate.app', on), Custom Dashboard (Customise), Brand Colors for charts (Customise), Unread Chat email notifications (off), Wall comment notifications (off).

On screen: Language, Currency, Enable Application Marketing by Default, Custom Dashboard, Brand Colors, Chat/Wall notification emails

Actions available: Select Language, Select Currency, Customise, toggles

Use case. Admin sets defaults for new users and decides whether calls are advertised on the vendor's public listing.

Example. With marketing on, a fictional new call form would appear automatically in accubate.app's public listing of open calls.

Configure site/app/setup/sites/item/integrations

Site Settings: Integrations

AI providers (0 of 4 configured): Anthropic, OpenAI, Google Gemini and Groq, each usable for the AI assistant, tool calling and form submissions once a key is added. Other integrations (0 of 2): Leegality (e-signatures and stamped documents) and Oblic (document verification and identity checks). Zoom Video SDK row at the bottom.

On screen: provider, Not configured, capabilities chips

Actions available: Add Integration

Use case. Admin connects AI, e-sign and verification services with their own keys.

Example. To use e-sign on a fictional AGRI UDAAN 10.0 onboarding round, the admin would add a Leegality token and enable E-Signature in that round.

Configure site/app/setup/sites/item/custom-options

Site Settings: Custom Options (Startup)

Tenant-level picklists (nomenclature) with sub-tabs General, Startup, Resources, Events; all still 'Using Default Options'. Startup: Stage of Startup (9: Ideation to Commercialised), Legal Status of the Firm (11), Revenue Model (4), Operation Type (2), Market Type (10: B2B ... C2G), Technology Readiness Level 1-9, Funding Stage (11), Milestone Type (10). General: Gender (4). Resources: Category (26), Best Suited For (5). Events: Category (16), Sub category (75).

On screen: option list name, Using Default Options, Current Options (n)

Actions available: Create Custom Options

Use case. Admin adapts the startup profile taxonomy to the incubator's language.

Example. An agri incubator could add 'FPO' as a legal status or replace the stage list with its own 'Idea / Field trial / First sales / Scale' ladder.

Configure site/app/setup/sites/item/defaults

Site Settings: Default Forms & Backgrounds

Site-wide defaults: login screen image (aidea.png, 7:6), grievance screen background, resource form, and the startup forms used everywhere: Patent, Copyright, Trademark (not set), Award, Publication, Investor Connect form and its request/accept/reject emails, Mentor Connect form ('Dummy Mentor connect form') and emails, Market Access form. Most are 'Not updated yet'. The About tab (not shot) holds legal and incubation-centre details, almost all 'Not updated yet' except India / Telangana / Hyderabad.

On screen: Login screen image, Patent/Copyright/Trademark/Award/Publication forms, Investor Connect form and emails, Mentor Connect form and emails, Market Access form

Actions available: edit (pencil) per item

Use case. Admin picks the standard forms behind startup IPR, awards and connect requests.

Example. The admin attaches a richer patent form so every incubated startup records filing number and status the same way.

Configure site/app/setup/sites/calendar

Site calendar

Month calendar for the site (working days, holidays and public calendar) with Today, previous/next, Month/Week switch and 'View Public Link'. It rendered empty: the schedule is loaded by a POST the read-only guard blocked, and the Setup card says 0 upcoming entries.

On screen: month grid, view switch

Actions available: View Public Link, Today, Previous/Next, Month options

Use case. Admin publishes holidays and programme dates for staff, mentors and startups.

Example. The admin would mark Sankranti holidays and the fictional AGRI UDAAN 10.0 pitch day so mentor bookings avoid them.

Monitor/app/setup/sites/usage/resources

Site Usage: Resources

Tabs Resources, Download Logs, Inbox, Login History, Video Usage. Storage Usage Trend by month (50.31 GB in Jan 2026 to 64.42 GB in Sep 2026), Storage by Modules for October 2026 (total 64.45 GB, 25,807 documents; application 58.57 GB / 23,050 docs, startup 5.23 GB / 2,134, pipeline 0.30 GB, user 0.20 GB ...), AI Usage (no information), Document Transfer Report and Emails (did not load: blocked POST reads), Organisation Users '24 / 24' (staff with admin or management roles, with role filter and Delete).

On screen: Storage Size, Storage Usage (GB-month), Storage by module, Total Documents, AI Usage, Organisation Users 24/24

Actions available: year/month pickers, Search (reports), Download, Delete (org user)

Use case. Super-admin checks storage, staff seats and logs, typically before renewal or an audit.

Example. The admin sees all 24 staff seats are taken and must remove one before adding a new cohort manager.

Create Startups pipeline/app/tools/mapping

Mappings (Tools): application to startup pipelines

List of 26 mappings, each From Pipeline (an Applications pipeline) To Pipeline (a Startups pipeline), Type 'Application -> Startup', with View and Delete. It is how a selected application becomes a startup record of the cohort.

On screen: From Pipeline, To Pipeline, Type

Actions available: Add New, View, Delete

Use case. PM links each cohort's funnel to its portfolio pipeline.

Example. A fictional 'AGRI UDAAN 10.0 Applications -> AGRI UDAAN 10.0 Startups' mapping would be added when the cohort's startup pipeline is created.

Create Startups pipeline/app/tools/mapping (View Mapping)

View Mapping (field-by-field)

Full-screen modal. Left: every question of every round of the application pipeline (Round 1 has 57 questions, Round 2 has 8). Right: the startup profile sections (Company Profile, Portfolio ...) where each profile field gets a 'Select Mapping' dropdown pointing to an application question; many remain unmapped. The portfolio side includes uploads such as founders' PAN and Aadhaar copies, bank passbook, MoA/AoA, logo and pitch deck.

On screen: application questions by round, startup profile fields, Select Mapping

Actions available: Close, Edit Mapping

Use case. PM avoids re-asking selected startups for data they already gave in the application.

Example. For the fictional AgroSense (fictional), 'Date of Incorporation/Registration' and 'Company Website' flow into its startup profile; unmapped fields like TRL must be filled again after onboarding.

Facts observed

Tenant: Site Id 'aideanaarm', 'a-IDEA, NAARM-TBI', time zone Asia/Calcutta; vendor Cunomial (footer 'Copyright 2026 Cunomial').
Accubate subscription: start 22 Jul 2021, end 31 Mar 2027 10:00 AM, 169 days left on 12 Oct 2026 (this is the renewal date the proposal was missing).
Dashboard counters: 25 programmes, 59 cohorts, 7,081 applications, 360 startups, 1 session, 0 courses, 2 surveys; 25 open grievances on the dashboard (Tools card says 53 open).
All 25 programmes are typed 'Incubation', including a hackathon, a conference, an FPO CEO course and a 'sensitization' entry; one programme (SISFs) has 0 cohorts.
Largest programmes by applications: Aggnite 1,251, AGRI UDAAN 1,160, NIDHI PRAYAS 1,094, Agribusiness Management Development Programme for FPOs 929, KRISHIBOOT 657, SIDBI Seed Fund 572.
AGRI UDAAN has 6 cohorts (2021, 5.0 to 9.0); AGRI UDAAN 7.0 had 257 applications and 17 startups, 17 evaluators, no programme/cohort managers or mentors attached; 9.0 (Sep 2026) had 3 applications and an inactive pipeline.
87 pipelines: 56 Application and 31 Startup; 80 active, 7 inactive; rounds per Application pipeline range from 1 to 4 or more.
Round types: Public (open link /ext/form/<pipelineId>/<round>/apply) or Private (applicant must verify email by OTP); each round has start/end date-time or 'no end date'.
Round editor tabs: General, Application, Application Form Design, Evaluation, Mentoring, Payment, E-Signature, Settings; Application has 10 toggles and Evaluation 16 toggles.
Payment links per round expire after a configurable period (default preview 7 days); payment request email uses {{Sid}} merge tags; Payments setup has 0 accounts configured.
Startup pipeline modules: Documentation, Canvas Model, Patents, Copyrights, Trademarks, Publications, Market Access, Awards, Documents, Portfolio Management; direct onboarding URL /ext/startup/apply/<pipelineId>.
Forms: 164 in the list (Setup card says 155); categories Application and Startup; labels REGULAR, UPDATES, PORTFOLIO; a typical first-round form has 43 questions (a later edition's Round 1 had 57).
Mail templates: 298 in the list (Setup card says 256); system templates locked against deletion.
Users: 6,252 total; Applicant 5,883, Startup owner 281, Evaluator 216, Administrator 20, Program Manager 6, Course Manager 6, Mentor 3, Cohort Manager 2, Guest 2, one each of Evaluation Manager, Funding Portfolio Manager, Fund Manager, Instructor, Portfolio Manager.
Organisation (staff) users seat counter shows 24 / 24 on Site Usage.
Access is scoped per role through a checkbox tree Site > Programme > Cohort.
Groups: 0; Partnership records: 0; Static data categories: 0; Site calendar: 0 upcoming entries; integrations: 0 configured.
Storage: 64.45 GB and 25,807 documents (Oct 2026); applications take 58.57 GB; growth about 14 GB in 2026 so far.
MFA for all users is off; language default English (US); currency not set and preview formatted ₹1,234,567.89 (Western grouping).
'Enable Application Marketing by Default' is on: new application forms are publicly listed on accubate.app.
AI is bring-your-own-key: Anthropic, OpenAI, Google Gemini, Groq (none configured; AI usage 'No information received'); e-sign via Leegality and verification via Oblic (not configured); Zoom Video SDK listed.
Default startup option lists: Stage of Startup 9, Legal Status 11, Revenue Model 4, Operation Type 2, Market Type 10, TRL 1-9, Funding Stage 11, Milestone Type 10; Resource categories 26; Event categories 16 with 75 sub-categories.
26 Application -> Startup field mappings exist under Tools > Mappings; the AGRI UDAAN 7.0 mapping leaves most startup-profile fields unmapped.
The startup portfolio profile asks for uploads of founders' Aadhaar and PAN, bank passbook/cancelled cheque, MoA/AoA and GST copies.
A legacy UI and legacy API coexist ('Click here to go back to the older view' on Users; api-legacy.accubate.app calls).

Strengths

The Setup hub is organised by life-cycle stage, with live counts, pinning and recently visited items.
A consistent, reusable pattern: each cohort gets an Applications pipeline (funnel) and a Startups pipeline (portfolio), linked by a field mapping.
Rich per-round control: public or OTP-gated private rounds, scheduling, auto-promote, duplicate-application check, edit-after-submit, SMS and email, AI-assisted form filling, payments with expiring links, e-signature.
Fine-grained evaluator controls (weighted scoring, conflict reporting, hide fields, hide peers' scores, allow promote/reject).
Role access scoped per site, programme or cohort, with multiple roles per person.
Editable taxonomies (stage, TRL, legal status, market type, funding stage) without code.
Transparent usage page: storage by month and module, seat counter, login and download logs.
Mail template library with categories, merge tags and locked system templates.

Gaps and friction

Setting up one call means visiting five separate builders (Cohorts, Pipeline, Form, Mail, Tools > Mappings) plus Users; nothing guides the order.
Drill-down links are unfiltered: '4 Cohorts' or '173 Applications' on a programme card and 'View All' on a cohort go to the full site-wide lists.
Program and cohort lists are huge image cards (cohorts page about 6,700 px) with no table view, open/closed status or call dates.
Programme type is meaningless (all 'Incubation'), and programmes are bent to hold hackathons, conferences, surveys and data-collection forms.
Cohort Timeline is empty on every cohort checked, so there is no structured call calendar; staff contact details are typed into free-text About.
Two partner concepts on one cohort page: partner logos are shown, yet 'Associated Partners: No partners added'.
Programme-level and cohort-level manager slots are empty (0 programme managers); access lives only in per-user checkbox trees, so 'who runs this cohort' is not visible on the cohort.
Dozens of round toggles, default off, with no presets or round templates; settings are re-done per round and per edition.
The pipeline editor autosaves ('Saved'), so a stray toggle changes a live call immediately; no draft/publish or visible change history.
Counts disagree between screens (forms 155 vs 164, templates 256 vs 298, users 6,253 vs 6,252, open grievances 25 vs 53).
Field mapping is manual and mostly incomplete, so onboarded startups re-enter data they already gave.
MFA is off for all users of a site holding 25,800 documents including identity papers; staff seats capped (24/24).
No Indian number formatting (₹1,234,567.89) and only English (US) as language default.
Calls are listed publicly on the vendor's marketplace by default.
AI is BYO-key to US providers with no data-residency option; nothing configured, so AI features are unused.
Founders' Aadhaar copies are collected in the portfolio profile.
Old and new UIs coexist; copy errors such as 'No Program Managers have access to this cohort' on a programme page.

For INQB Zone

Keep the model (programme > call/cohort > rounds > forms > selected startups) but make it one 'Call' workspace with steps: details, timeline, rounds, forms, jury, emails, publish.
Drop pipeline-to-pipeline field mapping: INQB's single founder-owned venture profile (B1) and application snapshots make onboarding a status change, not a data copy.
Ship round templates with sensible defaults (screening, due diligence, pitch day) that the PM edits (brainstorm B-rows on round templates), and show a plain summary of active rules.
Use draft and publish with an audit trail for live calls instead of autosave.
Make the call timeline mandatory and structured; feed it to the public directory of open calls and to the calendar.
Show the people on a cohort (PM, cohort managers, jury, mentors) on the cohort itself, and scope access per organisation, programme and cohort like Accubate does.
Every count must be a filtered, clickable link and must match across screens.
Use real programme types (incubation call, accelerator, grant scheme, hackathon, event, survey) so reports by type mean something.
Lakh/crore formatting, INR default and Indian languages from day one.
Enforce TOTP for admins and finance (INQB rule); never collect Aadhaar (INQB rule); keep public listing opt-in per call.
AI through OmniRoute with India-only processing for a-IDEA, no tenant BYO US keys.
Offer a usage page like Accubate's (storage by module, active startups against the plan's 150 band, staff seats, login history).
Accubate's licence for a-IDEA ends 31 Mar 2027: the MoU's month-7 review and the Phase 2 switch should land before then, ideally decided by about end of January 2027 (60 days before).

Calls, applications, evaluation and selection

This is the intake half of Accubate: a Programme Manager builds an application form, attaches it to a 'pipeline' (one call, e.g. KRISHIBOOT 10.0) made of numbered rounds, publishes Round 1 as a public apply link, then works the incoming applications round by round. Each round can have its own form (later rounds are 'Private', so only promoted applicants fill them), its own evaluation form (weighted criteria scored by assigned evaluators) and its own emails, payments, mentoring and e-signature settings. Staff promote, demote, reject or withdraw applications in bulk, watch evaluator workload and score analytics, and send promotion and rejection mails. A selected applicant is 'Onboarded', which copies it into a separate Startup pipeline (e.g. 'KRISHIBOOT- 9.0 Startups') where the post-selection life cycle starts. At a-IDEA the module is heavily used for intake (7,081 applications, 87 pipelines, 164 forms) but the in-app evaluation is used only for some calls (NIDHI PRAYAS 5th Call used 61 evaluators; KRISHIBOOT 9.0 and SIDBI Seed Fund 2026 selected without any evaluation form).

Create the pipeline (call) and its rounds
Configure each round: form, emails, design, evaluation, payment
Build and version the application form
Publish the public apply link and track visits
Receive applications (submitted or saved as draft)
Screen and filter applications in Round 1
Set up evaluators and the weighted scorecard
Assign evaluators; evaluators score
Review scores, evaluator analytics and rankings
Promote to the next round (private round forms, pitch/interest form)
Final selection and result mails
Onboard selected applicants into a Startup pipeline

Use cases

Programme Manager, founder, three evaluators, selection committee

AgroSense applies to KRISHIBOOT 10.0 and is selected (full walk-through)

Setup (a2-01, a2-02): the PM creates 'KRISHIBOOT 10.0 Applications' under the KRISHIBOOT programme, with Round 1 Public (open until 28 Oct 2026) and later adds Round 2 (Private, evaluation) and Round 3 (Private, pitch).
Form (a2-04 to a2-09): the PM duplicates last year's form, edits it to 24 questions including the ₹200 fee receipt and UTR, previews it, and can later audit its 35 saved versions.
Round rules (a2-03, a2-10): existing-application check on, submission email on, reminders to saved drafts on.
Publish (a2-11, a2-12): the apply link is shared; the Marketing tab shows 199 visits, 10 submitted, 4 drafts, 185 drop-outs.
Apply (a2-11): the AgroSense founder (fictional, precision-irrigation sensors) fills the public form and submits; gets the submission email and login credentials.
Screen (a2-14, a2-15, a2-17): after the deadline the PM filters Submitted, opens AgroSense's application, checks the fee receipt and UTR, adds an internal comment, and moves eligible ones to Round 2 with Move to Next Stage (promotion mail goes out).
Evaluation setup (a2-19, a2-20): the PM attaches a six-criterion /60 rubric to Round 2, enables conflict reporting, and adds three evaluators from the 216-person Evaluators directory through Manage Evaluators.
Scoring (a2-22, a2-21): each evaluator opens Pending Evaluation and scores AgroSense; the PM watches pending counts and sends a reminder to one late evaluator.
Shortlist (a2-23 to a2-26): the PM sorts Scores by average (AgroSense 47/60, 4th), checks the three evaluators' sheets and the evaluator-bias charts, then moves the top 20 to Round 3 and rejects the rest (rejection mails).
Pitch (a2-18, Meetings tab): Round 3 uses a private interest form (mode of participation online or physical); pitch slots would be scheduled in Meetings, but a-IDEA has no meetings recorded, so the pitch day and committee decision happen outside Accubate.
Selection and mails (a2-27, a2-28): the PM records the committee's result by promoting or rejecting in Round 3; the Mails log shows each result mail and its delivery report.
Onboard (a2-27, a2-29): the PM clicks Onboard on AgroSense; it appears with a rocket icon in the journey and is created in the 'KRISHIBOOT 10.0 Startups' pipeline, where the post-selection life cycle (profile, documents, updates, mentoring) begins.

Example. AgroSense (fictional) goes from public form on 5 Oct, to Round 2 on 29 Oct, scored 55/45/45 of 60 by three jurors, shortlisted 4th, pitches online in Round 3, and is onboarded as one of five KRISHIBOOT 10.0 startups.

Programme Manager

Chase drafts and late Round 2 forms

Open the pipeline and click the round in the stepper
Filters: Form Status = Saved or Not Filled
Select all and Send Announcement, or rely on 'Reminder Emails for Saved Applicants'

Example. Four KRISHIBOOT 10.0 applicants still have drafts three days before the deadline; the PM sends them a reminder.

Evaluation Manager

Balance and chase evaluators

Evaluations > Evaluators
Sort by Pending or Expired
Send Reminder to the late ones, or reassign through Manage Evaluators
Use Analytics to spot evaluators whose mean is far from the pool

Example. One of 61 NIDHI PRAYAS evaluators has 2 expired evaluations; the manager reassigns them so every application has 3 scores.

Admin

Audit a changed application form

Setup > Form
Row menu > History
Versions to see who saved when
Forms Comparison to compare two versions side by side

Example. An applicant says a question disappeared mid-call; the admin compares v34 and v35 and finds the MCA legal-name question was removed on 7 Oct.

Screens 29

Create the pipeline (call) and its rounds/app/setup/builder/pipelines

Pipelines (Setup > Pipeline)

Card grid of all 87 pipelines. Each card shows the pipeline name, Active/Inactive, programme type (Incubation), pipeline kind (Application or Startup), the parent programme and cohort, the number of rounds and the number of applications or startups, and the creation date.

On screen: Pipeline name, Active / Inactive badge, Incubation, Application / Startup badge, Programme link, Cohort link, Rounds count, Application(s) / Startup(s) count, Created on

Actions available: Add New, Add filter, Search Pipelines, Clear all, View/Edit, Delete

Use case. Programme Manager, when launching a new call: creates an Application pipeline under the programme's cohort, and a matching Startup pipeline for those who will be selected.

Example. The PM creates 'KRISHIBOOT 10.0 Applications' (1 round so far) under the 'KRISHIBOOT- Call for Incubation' programme; last year's 'KRISHIBOOT- 9.0 Startups' pipeline holds the 5 startups selected from 9.0.

Create the pipeline (call) and its rounds/app/setup/builder/pipelines/list/2773

Pipeline setup: rounds and round General tab

Auto-saving pipeline editor. Top bar toggles: Active, Display Startup Name, Hide Status (hide promoted/rejected/onboarded from applicants), Hide Round (applicants see 'Form-1, Form-2' instead of round names). Left column lists rounds as cards: Round 1 is Public with its apply URL (/ext/form/<pipeline>/<round>/apply), start and end date and status (Closed); Rounds 2 and 3 are Private. The right side shows the selected round's tabs; General holds 'Currently Active Round' and the promotion, rejection and withdrawal email switches.

On screen: Round cards (Type Public/Private, URL, Starts, Ends, 'no end date', Status), Tabs: General, Application, Application Form Design, Evaluation, Mentoring, Payment, E-Signature, Settings, Currently Active Round, Promotional Email, Rejection Email, Withdraw Email

Actions available: Edit title, add round (+ between cards), round gear settings, star (active round), Edit Title, Back

Use case. PM setting up the multi-round structure of a call before it opens, and switching which round is current as the call progresses.

Example. For a fictional 'Agri Seed Call 2027' the PM adds Round 1 (Public, open 1-30 Nov), Round 2 (Private, detailed proposal) and Round 3 (Private, pitch), and turns on the rejection email for Round 1.

Configure each round: form, emails, design, evaluation, payment/app/setup/builder/pipelines/list/2773?section=Application&round=1

Round settings: Application tab

Long list of switches for how the round's form behaves. Attaches a form template, sends login credentials on submission (Onboarding Email, 'Registration for new users' template), optional AI form submission, SMS, submission and draft-saved emails with CC, auto move / auto copy to another pipeline, auto onboard to a Startup pipeline on submission, reminders to saved applicants, auto promote, multiple applications per email, unique-answer validation across applicants, existing-application check by email or phone, and edit after submission.

On screen: Add Application + Form Template, Edit Application Access Mail, Onboarding Email, Allow AI Form Submission, Onboarding SMS, Submission Email + Mail Template + CC, Form Saved Email, Submission SMS, Auto Move Application, Auto Copy Application, Auto Onboard to Startup, Reminder Emails for Saved Applicants, Application auto Promote, Allow Multi application, Enable Unique Answer Validation, Existing Application Check, Allow Edit After Submission

Actions available: toggles, Edit / Change form template, Edit / Change mail template, Add CC

Use case. PM deciding the rules of intake for one round (duplicates, drafts, reminders, automatic moves).

Example. For the fictional call the PM switches on 'Existing Application Check' so AgroSense cannot apply twice with the same phone number, and 'Reminder Emails for Saved Applicants' for drafts.

Build and version the application form/app/setup/builder/form

Forms list (Setup > Form)

Table of 164 forms used by all modules: application forms per call and round, startup update forms and portfolio forms. Columns show title, category, label and status; creator names are blurred.

On screen: Title, Last Modified, Category (Application / Startup), Label (REGULAR, UPDATES, PORTFOLIO), Created By, Status (PUBLISHED), Actions

Actions available: Add New, Add filter, Search Form, row menu

Use case. PM or admin finding, reusing or cloning a form for a new call or round.

Example. The PM finds 'KRISHIBOOT 10.0 Application Form' and 'KrishiBoot 9.0 - Final Round Application' to reuse their questions for KRISHIBOOT 11.0.

Build and version the application form/app/setup/builder/form

Form row actions menu

The row menu of a form opened (nothing chosen). It offers Edit, Duplicate, Delete, Pin, Lock and History.

On screen: Edit, Duplicate, Delete, Pin, Lock, History

Actions available: Edit, Duplicate, Delete, Pin, Lock, History (opened read-only, next screens)

Use case. Admin duplicating last year's form, locking a live form against changes, or checking its change history.

Example. Before KRISHIBOOT 11.0 the PM duplicates the 10.0 form and locks the original so that live applications keep their questions.

Build and version the application form/app/setup/builder/form/51774

Form builder (preview mode)

The form opens in a preview of the live form with numbered questions and field widgets (text with character counters, email, phone, address with country, date, file upload). Top-right buttons switch to edit mode, print or close. The edit palette was not opened (read-only rule).

On screen: Form title, Numbered questions, Required asterisks, Character limits (250 / 5000), Upload your file

Actions available: Save, Edit, Print, Close

Use case. PM checking the form exactly as applicants will see it before opening the call.

Example. The PM previews question 13 'What is the problem statement...' (5000 characters) before publishing.

Build and version the application form/app/setup/builder/form/51774/history

Form History: Versions

Every save creates a version. The KRISHIBOOT 10.0 form is at v35; many versions are a minute or less apart, which shows saves are recorded as versions without a named release. Editor names are blurred.

On screen: Versions (v35 current ... v1), Updated At, Updated By

Actions available: Versions / ViewForm / Forms Comparison tabs, Close

Use case. Admin auditing who changed the form and when, for example after an applicant complains a question changed.

Example. A PM sees that v18 to v35 were made between 29 Sep and 7 Oct 2026, after the call opened.

Build and version the application form/app/setup/builder/form/51774/history/v35

Form History: View a version

Renders any chosen version of the form read-only (version picker 'Select Date'). The KRISHIBOOT 10.0 form has 24 questions: identity and contact, date of birth, designation, qualification certificate and founder photo uploads, entity type (individual / Pvt Ltd / LLP), focus area (15 agri options), stage (ideation to scale), website, problem, solution, value proposition, product photo, revenue model, funds raised, revenue band, IP, other incubation, and a ₹200 registration fee paid by bank transfer with receipt upload and UTR details.

On screen: Select Date (version), Question list as of that version

Actions available: version dropdown

Use case. PM or auditor checking which questions applicants saw on a given date.

Example. Checking whether AgroSense, which applied on 5 Oct, saw the 'Legal name as per MCA' question that existed in v34.

Build and version the application form/app/setup/builder/form/51774/history/compare

Form History: Forms Comparison

Side-by-side view of two versions (here v34 and v35) for spotting changes. It shows both rendered forms; the difference (v34 had a conditional 'Legal name of registered entity as per MCA' question and 'Select not more than 1' wording) has to be found by eye, there is no highlighting.

On screen: Left version picker, Right version picker, Two rendered forms

Actions available: version dropdowns

Use case. Admin reviewing what changed between two saves.

Example. The PM compares v34 and v35 to see that the MCA legal-name question was removed.

Configure each round: form, emails, design, evaluation, payment/app/applications (Settings button)

Quick Settings (from the applications list)

An auto-saving modal on top of the applications list for the current round: application start and end dates, the attached form template, the text on the apply button and 'Application auto Promote', with tabs Form, Form Design and Communications and an 'Advanced Settings' jump to the full pipeline editor. Shown for SIDBI Seed Fund 2026 Round 3 (an interest form open 23 to 28 Sep 2026).

On screen: Round stepper, Form / Form Design / Communications, Application Start Date, Application End Date, Form Template, Text on Button, Application auto Promote

Actions available: Edit, Change, Advanced Settings, Close

Use case. PM extending a deadline or swapping the form of the current round without leaving the list.

Example. The PM extends the fictional call's Round 2 deadline by three days from the list.

Publish the public apply link and track visits/ext/form/24431/1/apply

Public apply page (what a startup sees)

The public KRISHIBOOT 10.0 form on a green background: poster, 'Last Date to apply: 28 Oct 2026', description of the call, an 'Already Applied? Check your status' box, the 24 numbered questions, a Terms and Privacy consent checkbox, Submit and Save as Draft, and 'Powered by Cunomial'. Because a staff account was signed in, name and email came prefilled (blurred). The payment question shows a-IDEA's bank details (blurred here). Not filled or submitted.

On screen: Call title, Poster, Last date, Description, Check your status, Numbered questions, Consent checkbox

Actions available: Check (status), Upload your file, Submit, Save as Draft

Use case. Founder applying to a call from a link shared on social media or the a-IDEA website.

Example. The founder of AgroSense (fictional, precision irrigation) opens the link, fills the 24 questions, uploads the ₹200 fee receipt with the UTR and submits.

Publish the public apply link and track visits/app/applications/marketing

Marketing tab: apply-link funnel

Per tracked apply URL ('Default' plus any extra per-channel URLs) the page visits, submitted, currently saved and dropped-out counts as a bar. KRISHIBOOT 10.0: 199 visits, 14 applications, 10 submitted, 4 saved drafts, 185 dropped out.

On screen: Total applications, Total visits, Reference URL, Page Visits, Submitted, Currently Saved, Dropped Out

Actions available: Settings, Add New (tracking URL), Export to Excel, Filters, row menu

Use case. PM checking which outreach channel brings applicants and how many abandon the form.

Example. The PM creates a separate URL for a WhatsApp group and sees it brought 60 visits and 5 submissions.

Receive applications (submitted or saved as draft)/app/applications (Change Pipeline)

Applications: pipeline picker

The Applications module always shows one pipeline at a time; 'Change Pipeline' opens a searchable list grouped by programme with Active/Inactive filter. About 20 programmes and 50 application pipelines are listed (KRISHIBOOT 2021 to 10.0, NIDHI PRAYAS calls 1 to 5, BIRAC SEED FUND, NABARD CCF, AGRI UDAAN, Aggnite, SIDBI Seed Fund, RuTAG, MEITY SAMRIDH and others).

On screen: Search, Status: All / Active / Inactive, Programme group header (Incubation), Pipeline names

Actions available: select a pipeline

Use case. PM switching between the calls they manage.

Example. The PM switches from 'NIDHI PRAYAS 5th Call Application' to 'KRISHIBOOT 10.0 Applications'.

Screen and filter applications in Round 1/app/applications

Applications list for one pipeline (KRISHIBOOT 10.0)

Pipeline header with round stepper (here only Round 1, since the call is open), module tabs and a long bulk-action toolbar. The table lists 14 applications: ID (AIDE-xxxxxx), applicant name and email (blurred), journey dots per round, form status (Submitted / Saved) and applied date. There is no kanban or board view; the round stepper doubles as a stage filter.

On screen: Application Id, Applicant, Email, Journey, Form Status, Applied On, View 20/50

Actions available: Settings, Edit Columns, Send Announcement, Print to PDF, Export to Excel, Reject, Delete, Move to Next Stage, Demote, Withdraw, Onboard, Manage Evaluators, Move to another pipeline, Import, Update Tags, Help, Filters, Advanced Filter, Search Applications

Use case. PM screening new applications daily while the call is open, and bulk-acting on a selection.

Example. On 29 Oct the PM ticks the 9 complete KRISHIBOOT 10.0 applications, including AgroSense's, and clicks Move to Next Stage.

Screen and filter applications in Round 1/app/applications (Filters)

Filters panel (facets)

Facet filters with live counts: Applied On (date range, Today / Last 7 / Last 30 days), Current Status (Withdrawn, Active, On-Boarded, Not Shortlisted), Active Stage (counts per round) and Form Status (Submitted, Saved, Not Filled). Shown for KRISHIBOOT 9.0: Round 1 142, Round 2 133, Round 3 41, On-Boarded 5. A leftover search term from another session ('su') was active and is persisted per pipeline. 'Advanced Filter' opens an empty rule builder ('Add new filter').

On screen: Applied On, Quick Selection, Current Status, Active Stage, Form Status, Reset Filter

Actions available: radio filters, Advanced Filter, Reset Filter

Use case. PM narrowing to, for example, Round 2 applicants who have not filled the Round 2 form, to chase them.

Example. The PM picks Active Stage = Round 2 and Form Status = Not Filled and sends those 12 a reminder announcement.

Receive applications (submitted or saved as draft)/app/applications/all

All applications across pipelines (legacy page)

Older cross-pipeline table of all 7,081 applications with ID, applicant (blurred), pipeline and status with current round. A banner says a new and faster Applications page is available.

On screen: Application Id, Applicant, Pipeline, Status (Active + round)

Actions available: Print to PDF, Export to Excel, Send Announcement, Filters, Search Applications

Use case. Staff looking up an applicant without knowing which call they applied to.

Example. A founder phones to ask about 'my application'; staff search here and find it in KRISHIBOOT 10.0, Round 1.

Screen and filter applications in Round 1/app/applications/list/235259/view

One application (detail page)

Header with application ID, applicant name and email, applied date, pipeline and status badge, record navigation (Back, Previous, Next) and per-application actions. Tabs: Pipeline Journey (answers per round), Documents, Announcements, Comments, Evaluations. The tab bodies stayed empty here because the page's data calls are POST or PUT requests that the read-only guard blocked (see blocked_reads); the answers themselves are therefore not captured.

On screen: Application ID, Applicant, Applied on, Pipeline, Status, Pipeline Journey, Documents, Announcements, Comments, Evaluations

Actions available: Back, Previous, Next, Export to Excel, Print to PDF, Withdraw, Move to next stage, Demote, Reject, Reactivate, Update Tags

Use case. PM or evaluation manager reading one application in full, adding internal comments, and moving it on.

Example. The PM opens AgroSense's application, reads its Round 1 answers, notes 'strong field pilot in Nalgonda' in Comments and clicks Move to next stage.

Review scores, evaluator analytics and rankings/app/applications/analytics

Pipeline analytics (auto charts per question)

For the selected round, one bar chart per form question plus round status and form status. Shown for SIDBI Seed Fund 2026 Round 3 (30 applicants): all accepted the equity terms (₹45-60 lakh per startup in tranches), sector split, mode of participation in the pitch (19 online, 11 physical) and two cooperation pledges. Each chart can be downloaded or switched between pie, bar, doughnut and line.

On screen: Round Status, Form Status, One chart per choice question, Download All Charts

Actions available: Filters, Advanced Filter, Download All Charts, per-chart download / type switch / full screen

Use case. PM reporting the cohort profile to the committee or a funder.

Example. The PM downloads the sector chart of the 30 SIDBI finalists for the selection committee's briefing note.

Set up evaluators and the weighted scorecard/app/setup/profiles/evaluators

Directory: Evaluators

Directory of external people by role: Mentors, Investors, Evaluators, Program Managers, Cohort Managers, Portfolio Managers, Evaluation Managers. 216 evaluators are registered (names and emails blurred), each with an Access action; there is 1 Evaluation Manager.

On screen: Name, Email, Actions (Access), role tabs

Actions available: Filters, Search, Access

Use case. Admin maintaining the pool of experts who can be assigned to evaluate applications.

Example. The PM checks that the three fictional jurors for KRISHIBOOT 10.0 (an agronomist, an investor and an ICAR scientist) are in the Evaluators directory.

Set up evaluators and the weighted scorecard/app/setup/builder/pipelines/list/2773?section=Evaluation&round=2

Round settings: Evaluation tab (scorecard)

Attaches an evaluation form to the round and sets how evaluation works. NIDHI PRAYAS 5th Call Round 2 uses six criteria scored out of 10 (Problem Addressed, Innovation/Idea, Novelty/IP, Commercialization/Business Potential, Team/Innovator, Execution/Prototyping Plan; total 60) with an editable weight table. Other switches: evaluation timeline, automatic application scoring from answers, conflict reporting, evaluators may edit scores, auto-assign evaluators, let evaluators promote or reject, show tags, show round status, form status, submission date or application link, hide promoted or rejected, hide fields from evaluators (blind review) and let evaluators see scores.

On screen: Add Evaluation Form, Evaluation Timeline, Application Scoring, Allow Weighted Evaluation (Question / Original Score / Weighted Score), Report Conflict Applications, Allow Edit, Auto Assign Evaluator, Allow Promote, Allow Reject, Allow View Tags, Show Round Status, Show Round Form Status, Show Round Submission Date, Show Application Link, Hide Promoted Evaluations, Hide Rejected Evaluations, Hide Fields From Evaluator, Allow Evaluator To View Scores

Actions available: toggles, Edit / Change evaluation form, Edit weights, Edit Title, Delete (round)

Use case. Evaluation manager designing the rubric and the rules evaluators work under, before assigning.

Example. For KRISHIBOOT 10.0 Round 2 the PM attaches a six-criterion rubric, weights 'Team' at 15 instead of 10, switches on conflict reporting and hides applicant contact fields from evaluators.

Assign evaluators; evaluators score/app/applications/evaluation (Evaluators sub-tab)

Evaluations > Evaluators (workload per evaluator)

Per evaluator in the round: assigned, upcoming, pending, expired, evaluated and conflicted counts and their average score. NIDHI PRAYAS 5th Call Round 2: 61 of 120 available evaluators used, 485 evaluations (482 evaluated, 1 pending, 2 expired, 0 conflicted); most evaluators had 8 to 10 applications.

On screen: Evaluator(s) used, Evaluator(s) available, Total Evaluation(s), Evaluator, Assigned, Upcoming, Pending, Expired, Evaluated, Conflicted, Evaluator Average Score

Actions available: Add Evaluator, Download, Send Announcement, Send Reminder, Delete Evaluations, Filters, Search Evaluators

Use case. Evaluation manager chasing late evaluators and balancing load during the scoring window.

Example. Two days before the KRISHIBOOT 10.0 deadline the PM sees one juror with 4 pending and clicks Send Reminder.

Assign evaluators; evaluators score/app/evaluation

Evaluator's own page (entry point only)

The page an evaluator lands on: a pipeline selector ('All', Change) and two tabs, Pending Evaluation and Completed Evaluations. The list did not load because its data call is a POST the guard blocked, and the signed-in account is staff, so the scoring form itself was not seen.

On screen: Pipeline selector, Pending Evaluation, Completed Evaluations

Actions available: Change (pipeline)

Use case. External evaluator opening their queue from the assignment email.

Example. A fictional juror opens Pending Evaluation, sees AgroSense among 10 KRISHIBOOT applications, reads it and scores six criteria.

Review scores, evaluator analytics and rankings/app/applications/evaluation

Evaluations > Scores (ranking table)

Per application in the round: current status, evaluation status (3 / 3 done), total score (e.g. 145 / 180), average (48.33 / 60, 80.56%, coloured green or amber) and an options menu. Header cards: evaluators used, total evaluations, overall average (37.41 / 60, 62.34%). Status chips filter All / Active / Passed / Not Shortlisted / On-Boarded; columns are sortable, which is how staff rank. 161 applications in this round.

On screen: Application Id, Applicant, Current Status, Evaluation Status, Scores, Average, Actions

Actions available: Settings, Edit Columns, Send Announcement, Print to PDF, Export to Excel, Reject, Move to Next Stage, Demote, Onboard, Manage Evaluators, Import, Update Tags, sort by Average

Use case. Evaluation manager building the shortlist: sort by average, tick the top N, Move to Next Stage, reject or leave the rest.

Example. The PM sorts KRISHIBOOT 10.0 Round 2 by average; AgroSense is 4th at 47/60, so it is among the 20 moved to the pitch round.

Review scores, evaluator analytics and rankings/app/applications/evaluation (click an application ID)

Score breakdown for one application

Modal per application with round tabs: evaluations count, total, average, weighted total and weighted average, then one row per evaluator with assigned date, original and weighted score per criterion, and remarks (blurred). Evaluator names are visible to staff (blurred here).

On screen: Round tabs, Evaluations, Total Score, Average Score, Weighted Score, Weighted Average Score, Evaluator, Assigned On, per-criterion Original / Weighted, Comments/ Remarks

Actions available: View (one evaluator's sheet), Close

Use case. Evaluation manager checking spread between evaluators before the committee meeting.

Example. The PM sees AgroSense got 55, 45 and 45 out of 60; one juror gave 0 on 'Execution' and the PM asks why.

Review scores, evaluator analytics and rankings/app/applications/evaluation (View)

One evaluator's scorecard (Detailed View)

Read-only sheet of one evaluator's scores: for each criterion the original and the weighted score, then the free-text remarks (blurred). This is effectively the evaluator's filled scorecard.

On screen: Problem Addressed, Innovation/Idea, Novelty/ IP, Commercialization/ Business Potential, Team/ Innovator, Execution/ Prototyping Plan, Comments/ Remarks

Actions available: Close

Use case. PM reading a specific juror's reasoning when scores disagree.

Example. The PM reads juror 2's remark that AgroSense's sensor cost is not yet viable and shares the gist (without the juror's name) in feedback.

Review scores, evaluator analytics and rankings/app/applications/evaluation (Analytics sub-tab)

Evaluations > Analytics (evaluator and application reports)

Evaluator Report: assigned / evaluated / pending (485 / 482 / 3) and per-evaluator mean, median and standard deviation bars (means range from about 10 to 55 out of 60, a sign of strict and lenient evaluators). Application Report: evaluators per application (161 with 3, 1 with 2) and average score distribution (61-80%: 87, 41-60%: 56, 81-100%: 10, 21-40%: 8). Evaluator names on the axes are blurred.

On screen: Evaluator filter, Status, Mean (Average), Median, Standard Deviation, Evaluators Per Application, Average Score Distribution

Actions available: per-chart download / chart type / full screen

Use case. Evaluation manager spotting harsh or generous evaluators; Accubate shows the bias but does not correct for it.

Example. The PM notices one juror averages 17/60 against a pool mean of 37 and decides to discuss AgroSense's borderline score with the committee.

Final selection and result mails/app/applications (KRISHIBOOT- 9.0, Round 3)

Applications moving through rounds (journey) and onboarded

KRISHIBOOT 9.0 with three rounds. The Journey column shows a tick for each round passed, a grey dot for the round where the application sits, and a rocket icon where it was onboarded as a startup. Funnel for this call: 142 in Round 1, 133 reached Round 2, 41 Round 3, 5 onboarded.

On screen: Round stepper (Round 1 >> Round 2 >> Round 3), Journey icons (passed / current / onboarded), Form Status, Applied On

Actions available: Move to Next Stage, Demote, Reject, Withdraw, Onboard, Move to another pipeline

Use case. PM making the final selection in the last round and onboarding the selected applicants.

Example. After the pitch, the PM ticks AgroSense and four others in Round 3 and clicks Onboard; their journeys show the rocket.

Final selection and result mails/app/applications/mails

Mails tab (result announcements log)

Log of system mails for the pipeline, split into Promotional, Rejection, Withdrawal, Drafts & Submissions, Reminder and Announcements. SIDBI Seed Fund 2026 shows 98 'SIDBI SEED Fund 1st round - Result announcement' promotion mails sent on 1 Sep 2026, each with status SENT and a delivery report. Recipients blurred.

On screen: Subject, To, Type (Promote ...), Status (SENT), Created At, View Report

Actions available: View Report, category chips, pagination

Use case. PM proving that a result mail went out, or checking bounces.

Example. AgroSense says it never got the Round 2 invitation; the PM opens the Promotional log and the delivery report for its address.

Onboard selected applicants into a Startup pipeline/app/setup/builder/pipelines/list/24405

Startup pipeline: onboarding settings

The Startup pipeline that receives selected applicants. 'Onboarding through Applications' lists the application pipeline that feeds it (KRISHIBOOT- 9.0 Applications). Also: direct onboarding through its own apply URL (/ext/startup/apply/<id>), user onboarding email with login credentials, onboarding email, hide pipeline from startups, prompt incomplete profile, incubation completion reminder. Left toggles choose the startup-side modules (Documentation, Canvas Model, IPRs, Market Access, Awards, Documents, Portfolio Management) and tabs configure profile, documentation, updates, mentoring, evaluation and resources.

On screen: Onboarding through Applications, Onboarding through other Startup Pipelines, Direct Onboarding + Application Url, User Onboarding Email, Onboarding Email, Hide pipeline from Startups, Prompt Incomplete Profile on Dashboard, Incubation Completion Reminder, module toggles, tabs: Onboarding, Application/Portfolio & Company Profile, Documentation, Updates, Mentoring, Evaluation, Resource, Settings

Actions available: Add (source pipeline), toggles, Edit / Change mail template, Back

Use case. PM linking a call to the cohort pipeline, so that 'Onboard' on an application creates the startup record with a login.

Example. When AgroSense is onboarded from KRISHIBOOT 10.0, it appears in 'KRISHIBOOT 10.0 Startups', its founder gets login credentials, and the dashboard prompts it to complete its company profile.

Facts observed

7,081 applications in total across all pipelines (legacy All Applications page).
87 pipelines in Setup (Application and Startup kinds); the Applications picker lists about 50 application pipelines under about 20 programmes.
164 forms (categories Application and Startup; labels REGULAR, UPDATES, PORTFOLIO); the Setup hub tile said 155.
216 evaluators and 1 evaluation manager in the Directory; the Setup hub also shows 6,253 users, 59 cohorts and 256 mail templates.
Application IDs look like AIDE-######.
KRISHIBOOT 10.0 (open, last date 28 Oct 2026): 1 round so far, 14 applications (10 submitted, 4 saved), 199 page visits, 185 dropped out; 24-question form; ₹200 registration fee paid by bank transfer with receipt upload and UTR (not through the payment module); the form is at version 35.
KRISHIBOOT 9.0: 3 rounds; 142 in Round 1, 133 in Round 2, 41 in Round 3, 5 onboarded into 'KRISHIBOOT- 9.0 Startups'; no evaluation form in any round.
SIDBI Seed Fund Program at a-IDEA 2026: 3 rounds, 572 then 152 then 30 applications; no evaluation form in any round; Round 3 is an interest and terms form (equity, ₹45-60 lakh per startup in tranches; 19 online and 11 physical pitch participants); 98 Round 1 result mails sent on 1 Sep 2026.
NIDHI PRAYAS 5th Call (Nov-Dec 2024): 447 applications in Round 1, 161 in Round 2, 30 in Round 3. Round 2 used 61 of 120 evaluators, 485 evaluations (3 per application), six criteria scored 0-10 for a total of 60, overall average 37.41/60 (62.34%).
Round types are Public (has an apply URL /ext/form/<pipelineId>/<round>/apply) or Private (only promoted applicants fill it).
Pipeline-level switches: Active, Display Startup Name, Hide Status, Hide Round.
Per-round configuration tabs: General, Application, Application Form Design, Evaluation, Mentoring, Payment, E-Signature, Settings.
The form design tab supports a 4:1 poster, description, last date, social links, cohort partners, OTP verification by email or phone, supporting documents, drafts, post-submission and closure messages, public listing on accubate.app, Google Tag Manager, Facebook Pixel and multiple tracked apply URLs.
Evaluation supports weighted criteria, automatic scoring from answers, conflict reporting, auto-assignment, evaluator promote/reject rights, blind fields and an evaluation timeline.
Applications module tabs per pipeline: Applications, Evaluations (Scores, Evaluators, Analytics), Meetings, Analytics, Marketing, Payments, Document Builder, Mails, Requests.
Meetings (pitch scheduling), Payments, Document Builder (DOCX templates) and Requests were empty for SIDBI Seed Fund 2026.
Statuses: Active, Withdrawn, On-Boarded, Not Shortlisted; form status Submitted, Saved, Not Filled.
The selected pipeline and the list search term persist between visits and across browser tabs; the pipeline is not in the URL.
Opening an application's detail page fires a PUT to applicationEntities/<id> automatically (no click), apparently recording that it was viewed.

Strengths

Very complete multi-round model: each round has its own form, evaluation rubric, emails, payment, mentoring and e-signature settings, and later rounds can be private.
Weighted, criteria-based evaluation with evaluator workload, pending, expired and conflict tracking, reminders, and evaluator-bias analytics (mean, median, standard deviation per evaluator).
Clear journey visual per application (passed, current, onboarded) and live facet counts per round.
Form versioning with history, view-any-version and side-by-side comparison.
Apply-link funnel per tracked URL (visits, submitted, saved, dropped out) plus GTM and Facebook Pixel.
Plenty of automation switches: auto promote, auto move or copy to another pipeline, auto onboard to a startup pipeline, draft reminders, duplicate checks, unique-answer validation.
Auto-generated charts for every choice question of a round, downloadable for reports.
Mail log per pipeline with delivery reports, which settles 'I never got the mail' disputes.

Gaps and friction

Very wide toolbars: the applications list has 16 actions in one row (Reject, Delete, Move, Demote, Withdraw, Onboard, Move to another pipeline, Import...), so destructive and routine actions sit side by side.
Only one pipeline at a time; the choice is remembered per user, not in the URL, so two calls cannot be compared in two tabs and links cannot be shared.
No kanban or board view of stages; the round stepper is only a filter.
The application detail page loads its answers, evaluations and navigation through POST and PUT calls, and writes a record (PUT) just by opening it.
Evaluation is optional and often skipped: KRISHIBOOT 9.0 and SIDBI 2026 had no evaluation form, so the real selection (screening, pitch, committee) happens outside the system and only the outcome is recorded by promote or reject.
Evaluator bias is shown in charts but scores are not normalised; ranking is a plain sort on raw averages.
No visible pitch-day or committee-decision workflow; Meetings exists but was unused.
Fees are collected outside the payment module (bank transfer details inside a question, receipt upload and a free-text UTR field), so verification is manual.
Every save creates a form version (35 versions in about two weeks for one form), and Forms Comparison does not highlight differences.
Changing a live form during an open call is allowed; there is no warning or freeze.
Settings pages auto-save on every toggle with no confirm or undo, which is risky on a live call.
Two Applications pages coexist (legacy 'All applications' and the new pipeline page).
Public form prefills the signed-in staff user's name and email, which risks staff test entries.

For INQB Zone

Copy the round model (each round with its own form, rubric, emails and visibility) but present it as one clear call timeline with stage cards and a board view.
Keep the weighted rubric, conflict declaration, evaluator workload table and reminders; go further with the planned strictness-adjusted aggregation, so evaluator bias is corrected, not just charted.
Put the call and stage in the URL (/calls/<id>/stages/<n>) so links are shareable and several calls can be open at once.
Group bulk actions into a small primary set (Advance, Reject, Assign evaluators) with the rest in a menu, and confirm destructive ones.
Make the application detail page read-only by default: viewing must never write; log views in an audit table instead.
Model pitch day and the committee decision as real steps (slots, attendance, committee members' decisions, minutes) because a-IDEA runs them outside Accubate today.
Replace 'bank details in a question plus UTR text' with a proper fee step: payment link or UTR entry checked by the finance role, with a receipt generated by INQB Zone.
Version forms by publishing, not by every save, freeze questions once the first application arrives (changes create a new version for new applicants only), and highlight differences between versions.
Keep the apply-link funnel (visits, drafts, submitted, drop-off by channel) and per-question charts; they are cheap and PMs use them for reports.
Make onboarding a one-click 'Select and onboard' that turns the applicant's founder-owned profile into the incubatee record, instead of copying into a second pipeline that must be pre-configured.
Never prefill the public apply form with a staff account's identity; open it in a clean applicant context.
Keep a mail log per call with delivery status per recipient.

Startup portfolio and monitoring

After selection, Accubate moves a startup from an application pipeline into a 'startup pipeline' (one per programme cohort, e.g. 'a-IDEA Incubation Startup Details 2026 Startups'), where it gets an ID (AIDE-S#####), a membership status (Active, Graduated or Dropped off) and a profile whose modules are switched on per pipeline in the pipeline builder (documentation, IPRs, awards, documents, portfolio form, regular updates, mentoring, evaluation, resources). The Startups menu offers a global portfolio of all 360 startups (grid or table, a large filter panel, IPR, connect-request and engagement registers) and, per pipeline, a workspace with tabs for Startups, Tasks, Milestones, Evaluations, Fundings, Meetings, Connects, Analytics and Announcements. Progress and KPI collection is form-based: the manager attaches a 'Portfolio Form' and optional 'Updates' forms to a pipeline and watches a Not Filled / Saved / Submitted badge per startup; there is no KPI time series. At a-IDEA almost every monitoring feature is configured but empty (no milestones, tasks, evaluations, meetings, updates, engagements or connect requests in any pipeline checked), so in practice the portfolio module is used as a register of who is incubated in which cohort. The individual startup profile page could not be captured: it loads through a POST call that the read-only guard blocks.

Configure the startup pipeline (profile modules, onboarding rules, portfolio form, updates)
Onboard selected startups into the pipeline (from an application pipeline, direct, or by import)
Browse and filter the whole portfolio
Collect portfolio data and regular updates (KPIs)
Track milestones, tasks, evaluations and meetings
Analyse the cohort
Track IP and awards
Handle mentor, investor and market-access connect requests
Log engagements
Record funding and tranches
Change status: Active to Graduated or Dropped off
Publish directories

Use cases

Programme Manager

PM reviews AgroSense's quarterly KPIs and flags a missed milestone

Startups > Change Pipeline > choose the seed-fund cohort
Read the Portfolio column: AgroSense (fictional) shows 'Saved', not 'Submitted'
Open the startup's profile to read the portfolio form answers (profile page could not be captured)
Open the Milestones tab: in Accubate the milestone list is empty unless someone created milestones, so 'pilot with 100 farmers by month 6' would have to be added by hand first
Send Announcement to the startup asking it to submit, and hold the tranche outside the system

Example. AgroSense (fictional), a precision-irrigation startup, reports 60 farmers instead of 100; the PM can see only that the form was saved, has no KPI trend to compare with last quarter, and records the missed milestone in a spreadsheet.

Programme Manager

Onboard a newly selected cohort

In the pipeline builder, link the application pipeline under 'Onboarding through Applications' and switch on the needed modules
Enable 'User Onboarding Email' so each startup receives login credentials
Move selected applicants into the startup pipeline (or Import Startups)
Check the pipeline table: each startup appears Active with its onboarding date

Example. Twelve KRISHIBOOT 10.0 winners, including AgroSense (fictional), are onboarded in one batch on 1 November.

Programme Manager

Graduate a startup at the end of incubation

Optionally enable 'Incubation Completion Reminder' to be warned before the expected graduation date
In the pipeline table, change the row's status dropdown from Active to Graduated
The startup stays in the global register and keeps any other pipeline memberships

Example. AgroSense (fictional) completes 24 months; the PM sets it to Graduated in the 2024 incubation pipeline. No exit reason, outcome or alumni follow-up is captured.

CEO / Programme Manager

Find startups for an investor meet

Startups > All startups > Filters
Tick Domain = Precision Agriculture, TRL 7-9, Funding Stage = Grant / Government Funded
Switch to List view and Export to Excel

Example. Eight startups match, among them AgroSense (fictional); the list goes to the investor ahead of the meet.

IP cell / Programme Manager

Report incubatee IP to a funder

Startups > IPRs > Patents
Filter by programme or search, read filing and issue dates and status
Export to Excel for the report

Example. The annual NIDHI report lists two patents filed by AgroSense (fictional), one granted and one under examination.

Screens 20

Configure the startup pipeline (profile modules, onboarding rules, portfolio form, updates)/app/setup/builder/pipelines/list/24380

Startup pipeline builder: modules and onboarding rules

The settings page of one startup pipeline (the 2026 incubation cohort). A left panel of switches decides which modules the startup profile has: Active, Documentation, Canvas Model, IPRs (Patents, Copyrights, Trademarks, Publications), Startup Connect (Market Access) and Others (Awards, Documents, Portfolio Management). The Onboarding tab lists the application pipeline that feeds this pipeline and holds the onboarding rules. In this pipeline only Active and Documentation are on.

On screen: Module switches (Active, Documentation, Canvas Model, Patents, Copyrights, Trademarks, Publications, Market Access, Awards, Documents, Portfolio Management), Tabs: Onboarding, Application/Portfolio & Company Profile, Documentation, Updates, Mentoring, Evaluation, Resource, Settings, Onboarding through Applications (1), Onboarding through other Startup Pipelines (0), Direct Onboarding, User Onboarding Email (login credentials), Onboarding Email, Hide pipeline from Startups, Prompt Incomplete Profile on Dashboard, Incubation Completion Reminder (before expected graduation date)

Actions available: Toggle each module, Add onboarding source pipeline, Edit / Change email template, Back, Rename pipeline (pencil)

Use case. The incubation manager sets this up once per cohort before onboarding, deciding what a startup must keep up to date during incubation.

Example. Before KRISHIBOOT 11.0 opens, the PM clones last year's settings, turns on Patents and Portfolio Management, and enables the incubation-completion reminder so she is warned 30 days before AgroSense (fictional) is due to graduate.

Configure the startup pipeline (profile modules, onboarding rules, portfolio form, updates)/app/setup/builder/pipelines/list/720?section=Portfolio

Pipeline builder: application data, company profile and portfolio form

For an older funding cohort (NABARD CCF 1.0) the builder shows three data sources for the profile: persist chosen fields from the application form, extra company-profile fields, and a Portfolio Form the startup must fill. Each links to a form built in the form builder. This is how Accubate collects post-selection data such as KPIs.

On screen: Application Form (persist applicant data) + linked startup form, Extra Information in Company Profile, Portfolio Form + linked form ('... Startups Selected for Funding'), Module switches: Patents, Copyrights, Trademarks, Awards, Documents, Portfolio Management on

Actions available: Toggle each source, Edit form, Change form

Use case. The PM decides which application answers carry over and which portfolio questions (revenue, team size, funding raised) the startup must answer after selection.

Example. The PM attaches a 'Seed-fund portfolio' form asking for monthly revenue, farmers served and grant utilisation, so every funded startup such as AgroSense (fictional) fills it after onboarding.

Collect portfolio data and regular updates (KPIs)/app/setup/builder/pipelines/list/24380?section=Updates

Pipeline builder: regular updates (empty)

The Updates tab is where a manager would define recurring update forms ('This will allow you to collect regular updates from the startups'). No update is configured in the main 2026 incubation pipeline or in the NABARD 1.0 pipeline.

On screen: Explanatory line, Empty list of update schedules

Actions available: Add New (update)

Use case. Meant for monthly or quarterly progress reporting; a-IDEA does not use it.

Example. A PM could add a 'Quarterly KPI update' due on the 5th of each quarter; AgroSense (fictional) would then see a pending update on its dashboard.

Onboard selected startups into the pipeline (from an application pipeline, direct, or by import)/app/startups

Startups workspace: choose a startup pipeline

The Startups menu opens on one pipeline (last used). 'Change Pipeline' opens a searchable picker grouped by programme (each tagged 'Incubation'), with an Active/Inactive filter. About 31 startup pipelines exist, from 2018 seed-fund cohorts to the 2026 incubation cohort, plus FPO groups.

On screen: Search, Status: All / Active / Inactive, Programme heading + type 'Incubation', Pipelines under each programme

Actions available: Select pipeline

Use case. A PM switches between cohorts before working on their startups; every tab of the workspace is scoped to the chosen pipeline.

Example. The PM picks 'NIDHI SSS 2022 3rd call Funded Startups' to check which seed-fund startups have submitted their portfolio forms.

Onboard selected startups into the pipeline (from an application pipeline, direct, or by import)/app/startups/list

Pipeline workspace: startups of one cohort

The 2026 incubation pipeline holds 131 startups, all onboarded at the same minute (a bulk import) and all Active. The table shows ID, startup, founder and email, onboarding date, an inline status dropdown and milestone progress (0 / 0 for every row). Tabs across the top give the cohort's tasks, milestones, evaluations, fundings, meetings, connects, analytics and announcements.

On screen: Startup Id, Startup, Founder, Email, Onboarding Date, Status (dropdown), Milestones (done / total), Filter chips: All, Active, Graduated, Dropped off, Advanced Filter, List / Grid

Actions available: Settings, Edit Columns, Send Announcement, Export to Excel, Delete, Move (to another pipeline), Import Startups, Update Tags, Change Pipeline

Use case. The PM's daily list of the cohort: who is in it, since when, and their status.

Example. After the selection committee, the PM imports the 12 selected startups of KRISHIBOOT 10.0 and checks that AgroSense (fictional) appears as Active with today's onboarding date.

Browse and filter the whole portfolio/app/startups/all

All startups: grid view (default)

Global register of all 360 startups across programmes, 50 per page, as cards. Each card shows the startup ID and name (many still read 'Startup Name', i.e. the profile was never completed), the founder's name and email, status, and every pipeline the startup belongs to with its date range ('09 Sep 2026 - Present').

On screen: Startup ID + name, Status badge, Founder name + email, Pipelines with start date - Present, View Profile link

Actions available: Export to Excel, Send Announcement, Cleanup Suggestion(s), Filters, Search Startups, List / Grid, Page size, Delete (per card), View Profile

Use case. Used to find any startup regardless of cohort and to see its programme history at a glance.

Example. An investor asks about AgroSense (fictional); the PM searches the register and sees it went through KRISHIBOOT 7.0 and then the 2026 incubation pipeline.

Browse and filter the whole portfolio/app/startups/all

All startups: list (table) view

The same register as a sortable table: Startup Id, Startup, Founder, Email, Pipeline(s), Status and a Delete action. Every row sampled (first and last page) is Active.

On screen: Startup Id (sortable), Startup (sortable), Founder (sortable), Email (sortable), Pipeline(s), Status, Actions

Actions available: Delete, Export to Excel, Send Announcement, Sort columns, First / Previous / 1-5 / Next / Last Page

Use case. Quick scanning and export of the full portfolio, for example for an annual report to the funding ministry.

Example. The CEO exports the table to Excel to count how many startups were incubated across all NIDHI and BIRAC cohorts.

Browse and filter the whole portfolio/app/startups/all

All startups: filter panel

Clicking Filters expands an inline panel of checkbox lists and date ranges. Below the visible top part it continues with Legal Status, Domain, Sector, Country (enables State), TRL 1-9 and Funding Stage. Sector values are free text from forms, so the list has duplicates and typos.

On screen: On-Boarding Date from/to + 'Filter by earliest onboarding date' (first cohort only), Date of Registration from/to, Programs (25), Cohorts (~59), Pipelines (31), Stage (Ideation ... Commercialised, 9 values), Legal Status (11), Domain (~30), Sector (~60 free-text), Country -> State, Technology Readiness Level 1-9, Funding Stage (Bootstrapped ... Series C, Grant, Not Funded Yet)

Actions available: Tick filters, Pick dates, Search Startups

Use case. Segmenting the portfolio for a scheme report, a demo day or a call for nominations.

Example. For a drone-spraying investor meet, the PM filters Domain = Precision Agriculture, TRL 7-9 and Funding Stage = Grant / Government Funded and finds AgroSense (fictional) among eight matches.

Browse and filter the whole portfolio/app/startups/all

All startups: cleanup suggestions menu

A 'Cleanup Suggestion(s)' menu (sparkle icon) offers 'Cleanup Startups' and 'Cleanup Startup's Data', a data-hygiene helper for duplicate or incomplete startup records. The options were not opened.

On screen: Cleanup Startups, Cleanup Startup's Data

Actions available: Cleanup Startups, Cleanup Startup's Data

Use case. An admin tidies the register when the same venture has been created twice through different calls.

Example. The admin merges two records of AgroSense (fictional) created when it applied to AGRI UDAAN and to KRISHIBOOT with different emails.

Collect portfolio data and regular updates (KPIs)/app/startups/list (pipeline: NABARD CCF Investment Support 1.0 Startups)

Pipeline workspace with portfolio-form status

In a pipeline where Portfolio Management is on, the table gains a Portfolio column (Not Filled, Saved, Submitted) and a Portfolio Manager(s) column ('-' for all five startups). This is the only KPI-collection signal a manager sees in the list: whether the portfolio form has been submitted, not what it says. Milestones read 0 / 0.

On screen: Onboarding Date, Status, Portfolio (Not Filled / Saved / Submitted), Portfolio Manager(s), Milestones

Actions available: Manage Portfolio Manager(s), Import Startups, Move, Update Tags, Send Announcement, Export to Excel

Use case. The PM chases startups whose portfolio form is Not Filled and assigns portfolio managers to watch each startup.

Example. The PM sees AgroSense (fictional) still 'Saved' two weeks after the deadline and sends it an announcement asking it to submit its quarterly numbers.

Track milestones, tasks, evaluations and meetings/app/startups/milestones

Pipeline workspace: milestones (empty)

The Milestones tab of a pipeline. It was empty ('No Milestones Found') in every pipeline checked (2026 incubation, NIDHI SSS 2022, BIRAC Seed 2018, NABARD 1.0, older incubation). Tasks (To do / In progress / Done), Evaluations, Meetings (Upcoming / Completed / Cancelled), Connects and Announcement tabs were also empty.

On screen: Filters, Empty state

Actions available: Add New, Add a Milestone

Use case. Intended for setting cohort or startup milestones (for example tranche conditions) and tracking completion, which feeds the Milestones x / y column.

Example. A PM would add 'Field pilot with 100 farmers by month 6' for AgroSense (fictional); at the quarterly review she flags it as missed and holds the next tranche.

Analyse the cohort/app/startups/analytics

Pipeline analytics: company profile charts

Bar charts built from company-profile fields for the 131-startup 2026 pipeline: domain, sector, legal status, stage, women-led, TRL, revenue generated, revenue band, funding stage, revenue model, operation type, market type (B2B, B2C, B2G...), date of registration, social media presence. Most charts show only about five responses, so few startups have filled the profile. Sub-tabs Application (no form here) and Milestones (none) were empty.

On screen: Total Startups : 131, Domain / Sector distribution, Legal Status, Stage of Startup, Is Women Led, TRL, Has Revenue Been Generated?, Revenue Distribution (0-10L, 50L-1Cr, 1Cr-5Cr), Funding Stage, Revenue Model, Operation Type, Market Type, Date of Registration, Social Media Presence

Actions available: Download All Charts, Per-chart download / chart type / fullscreen, Filters, Advanced Filter

Use case. Quick cohort profile for a scheme report or board meeting.

Example. For the annual DST report the PM downloads the women-led and TRL charts for the 2026 cohort.

Track IP and awards/app/startups/iprAnalytics/patents

IPR register: patents

Portfolio-wide IP register with sub-tabs Copyrights, Patents, Trademarks, Awards and Publications. Patents (about 10 rows) list title, patent number or temporary application number, startup, founder, abstract, complete specification, issue date, applicant and inventor names, countries and addresses, filing date and status (e.g. 'Under Examination'). Copyrights, Trademarks and Publications are empty; Awards has a page of entries (title, startup, description).

On screen: Title, Patent Number, Startup Id / Startup, Founder / Email, Abstract, Complete Specification, Issue Date (with age), Applicant Name / Country / Address, Inventor Name / Country / Address, Filing Date, Status

Actions available: Export to Excel, Filters, Advanced Filter, Search Patents, Row checkboxes

Use case. The incubator reports IP generated by incubatees to funders and checks filing status.

Example. The IP cell sees that AgroSense's (fictional) soil-sensor patent has been 'Under Examination' for 18 months and books it a session with a patent attorney.

Handle mentor, investor and market-access connect requests/app/startups/connectAll

Connect requests (mentor, investor, market access)

A queue of requests raised by startups to meet a mentor, an investor or a market-access partner, with All / Pending / Approved / Rejected chips. Empty for all three types ('No New Connect Request Received'); the same tab inside a pipeline is also empty.

On screen: Mentor Connect, Investor Connect, Market Access, Status chips: All, Pending, Approved, Rejected, Search

Actions available: Export to Excel, Filters, Approve / Reject (per request, not seen)

Use case. The PM triages startup requests for introductions and approves those worth the mentor's or investor's time.

Example. AgroSense (fictional) requests an investor connect with an agri-fund; the PM approves it and the request moves to Approved.

Log engagements/app/startups/engagements

Engagements: leaderboard

Engagements record a startup's participation in incubator activities, ranked on a Leaderboard, with a Startups Engagements History and an Engagements catalogue. All three are empty at a-IDEA.

On screen: Leaderboard, Startups Engagements History, Engagements, Search Engagements

Actions available: Add Engagement, Add Startup Engagement, Import Startup Engagements, Export to Excel, Filters

Use case. Meant to show which startups are active in the programme (workshops attended, events, office hours).

Example. A PM would log that AgroSense (fictional) attended four masterclasses and a demo day, putting it near the top of the leaderboard.

Record funding and tranches/app/startups/funding

Pipeline workspace: funding recipients

The Fundings tab of a pipeline has Nominations (unique startups, unique fundings, active, rejected and onboarded nominations) and Recipients (total fund allocated and disbursed). All zero in the pipelines checked, including the seed-fund cohorts.

On screen: Nominations: Unique Startups, Unique Fundings, Active, Rejected, Onboarded, Recipients: Unique Startups, Unique Fundings, Total Fund Allocated, Total Fund Disbursed

Actions available: Add New, Send Announcement, Export to Excel, Filters

Use case. Links a cohort's startups to funding schemes and tracks allocation against disbursement.

Example. The PM nominates AgroSense (fictional) for the seed fund; once approved it shows ₹10 L allocated and ₹4 L disbursed in the first tranche.

Record funding and tranches/app/funding/recipients

Funding: all recipients

The global Funding module (Grant, Equity and Debt funds, Demo Days 'Coming Soon', All Nominations, All Recipients). No funding programmes exist (₹0 everywhere); one recipient record shows ₹2,50,000 disbursed with no funding or allocation linked. Its 'Tranche started on' value equals the current time on every reload, i.e. a missing date is displayed as 'now'.

On screen: Recipient Id (AIDE-FR#####), Recipient, Recipient Name, Email, Funding, Fund Allocated, Fund Disbursed, Tranche started on, Journey icon

Actions available: Send Announcement, Export to Excel, Filters, Search Recipients

Use case. Finance tracks money given to incubatees across schemes.

Example. The finance officer looks up AgroSense (fictional) to confirm the second tranche of ₹2.5 L was released before its utilisation certificate falls due.

Change status: Active to Graduated or Dropped off/app/startups/list

Startup status: Active, Dropped off, Graduated

Status is changed inline from a dropdown on each row of the pipeline table. Only three values exist: Active, Dropped off, Graduated. The status belongs to the startup's membership of that pipeline, not to the startup. No startup in the main incubation pipeline is Graduated or Dropped off, and every startup sampled in the global list is Active. No exit, alumni or 'on hold' states, no reason or date is asked in the dropdown.

On screen: Status dropdown: Active / Dropped off / Graduated

Actions available: Choose a status (not done)

Use case. At the end of incubation the PM graduates the startup or marks it dropped off.

Example. After its final review AgroSense (fictional) is set to Graduated in the 2024 cohort while remaining Active in the 2026 seed-fund pipeline.

Publish directories/app/directory

Public mentor directory

The public page (outside the app) with Filters, Search and Grid / Table / List views. It shows 'No mentors available': no mentor has been published to it.

On screen: Filters, Search, Grid View / Table View / List View

Actions available: Filter, Search, Switch view

Use case. Outsiders and founders browse mentors without logging in.

Example. A prospective applicant to AGRI UDAAN checks which post-harvest experts mentor at a-IDEA.

Facts observed

Home dashboard: 25 programmes, 59 cohorts, 7,081 applications, 360 startups, 1 mentoring session, 0 courses, 2 surveys
360 startups in the global register; IDs follow AIDE-S#####; funding recipients follow AIDE-FR#####
87 pipelines in the pipeline builder, about 31 of them startup (portfolio) pipelines, the oldest from 2018 seed-fund cohorts
Main 2026 incubation pipeline: 131 startups, all onboarded in the same minute on 09 Sep 2026 (bulk import), all Active, 0 Graduated, 0 Dropped off
Many startups in the register show the placeholder 'Startup Name' instead of a name, i.e. the profile was never completed
Statuses available: Active, Dropped off, Graduated, set per pipeline membership through an inline dropdown; every startup sampled on the first and last page of the global list is Active
Milestones column reads 0 / 0 for every startup seen; Milestones, Tasks, Evaluations, Meetings, Connects, Announcement and Updates are empty in every pipeline checked
Company-profile analytics for the 131-startup pipeline are based on about five responses per chart
IPR register: about 10 patents, a page of awards, 0 copyrights, 0 trademarks, 0 publications
Connect requests (mentor, investor, market access): none; engagements: none
Funding module: no grant, equity or debt funding programmes (₹0); one recipient with ₹2,50,000 disbursed; Demo Days marked 'Coming Soon'
'Tranche started on' shows the current time when no date is stored (changed from 10:52 pm to 10:57 pm between two reloads)
Directory has only a Mentor Directory; the public mentor page shows 'No mentors available'
Pipeline resource perks offered: Amazon AWS credits, Google Cloud Startup Program, Onsurity TeamSure, Razorpay (0 of 4 enabled in the pipeline checked)
Pipeline mentoring settings include anchor (long-term) versus one-time mentoring, mentee and mentor feedback forms, general feedback, hiding chosen profile fields from mentors and even from administrators
Filter panel offers 12 facets; the Sector facet has about 60 free-text values with duplicates and typos
Changing a list filter tries to save it as a user preference (PUT user-list-filters/startup-list); the chosen pipeline is remembered between tabs

Strengths

One global register of every startup with its full programme history (pipelines with date ranges), plus a per-cohort workspace
Profile modules are switchable per pipeline, so a seed-fund cohort can demand IP and portfolio data while an FPO cohort stays light
Application data can be carried into the startup profile, avoiding re-entry
Rich filter set (stage, TRL, funding stage, legal status, domain, programme, cohort, dates) and Excel export everywhere
Portfolio-wide IP register with patent detail (numbers, dates, status, inventors)
Useful operational switches: onboarding email with credentials, prompt for incomplete profile, incubation-completion reminder tied to expected graduation date, hide pipeline from startup
Fine-grained control over what mentors (and even administrators) can see of a startup's data

Gaps and friction

KPI collection is a one-off form with a Not Filled / Saved / Submitted badge; there are no KPI time series, targets, trends or traffic lights for a manager to review
Monitoring features exist but are unused at a-IDEA: no milestones, tasks, evaluations, meetings, updates, engagements, connect requests or funding records, so the module works as a register only
Company profiles are largely unfilled (about 5 of 131 answered; many records named 'Startup Name'), so analytics are not meaningful
Status model is thin: only Active, Dropped off, Graduated; no on-hold, exited, acquired or alumni state, no reason, date or outcome captured, nothing that follows a startup after graduation
Status is a one-click inline dropdown on the list with no visible confirmation, easy to change by mistake
Every tab is scoped to one pipeline chosen from a long picker; there is no cross-cohort view of milestones, funding or KPIs
Free-text sector values make filters messy (duplicates and typos)
Funding records can exist without a linked funding programme or allocation, and a missing tranche date is shown as the current time
Directory holds only mentors (and none are published); no startup or alumni showcase
Very dense action bars (Settings, Edit Columns, Send Announcement, Export, Delete, Move, Import, Manage Portfolio Managers, Update Tags) with destructive actions next to everyday ones; 'Delete' sits on every startup card

For INQB Zone

Copy the idea of one founder-owned startup record with a clear history of programme memberships, each with its own status and dates
Make progress reporting a real time series: scheduled monthly or quarterly reports with fixed KPI fields, targets per startup, trend charts and a red / amber / green flag the PM can act on, rather than a form-submitted badge
Tie milestones to tranches (late or missed milestone holds the next release) and show milestone status across all cohorts in one view
Seed sensible defaults so monitoring works out of the box (a standard KPI set, default milestones per programme template) instead of empty builders that nobody configures
Use controlled vocabularies for sector, domain and stage to keep filters and analytics clean
Richer life-cycle states (applicant, incubated, on hold, graduated, dropped, exited / acquired, alumni) with reason, date and an alumni check-in after graduation
Put status changes and deletions behind a confirmation with a reason, and keep Delete off the everyday cards
Prompt founders to complete the profile at onboarding and show the PM a completeness score per startup
Keep a portfolio-wide IP register and a per-cohort analytics page, but compute charts only on fields that are actually collected and show response counts
Offer a public startup directory or traction page, opt-in per startup, alongside the mentor directory

Mentoring, events and learning

Accubate's support-services layer has three modules: Mentoring (mentor-startup relationships, meetings, availability, feedback and analytics), Events (an event manager) and Learning (scheduled sessions with QR attendance, self-paced courses and a reference library), plus a personal calendar that shows sessions and meetings. Mentoring is configured and run per pipeline (a programme intake such as 'AGRI UDAAN 8.0 Startups'): the Programme Manager switches pipeline with 'Change Pipeline' and every tab (Relationships, Meetings, Mentors, Mentees, Feedbacks, Analytics, Requests) is scoped to that pipeline. The feature set is rich on paper (anchor vs one-time mentoring, approval rules, hidden startup fields, mentor slot booking, two-way feedback), but a-IDEA does not use it in practice: across 20 startup pipelines checked there are 0 mentoring relationships and 0 meetings, one pipeline has a single mentor (an a-IDEA staff member), there are 0 events, 0 courses, 0 library items and one 'Test Session'. These modules sit in the 'support during incubation' stage, after onboarding and before progress reporting and graduation.

Configure mentoring per pipeline (Setup > Pipeline > Mentoring)
Build the mentor pool (Setup > Directory > Mentors; public mentor directory)
Pick the pipeline to work in (Change Pipeline)
Add mentors to the pipeline and set their availability / booking window
See the pipeline's mentees (startups)
Receive mentor-connect requests
Create relationships (anchor or one-time) and schedule meetings
Collect mentor and mentee feedback
Track mentoring analytics
Run events
Run learning: sessions (attendance, recordings, feedback), courses, library
See everything on the personal calendar

Use cases

Founder, Programme Manager, Mentor

Startup asks for a mentor; PM matches; session held; feedback recorded

Admin switches on 'Raise Mentor Connect Request', 'Anchor Mentorings' (with approval), and 'Mentee's/Mentor's Feedback' in Setup > Pipeline > Mentoring for the cohort's pipeline.
Admin registers the mentor in Setup > Directory > Mentors; PM adds her to the pipeline (Mentoring > Mentors > Add Mentor).
Mentor or PM sets Availability: 45-minute slots, 5-minute buffer, weekly hours, date overrides; Booking Window opens her slots for the programme.
Founder raises a mentor-connect request with the configured form; it appears under Mentoring > Requests (auto-rejects after 7 days if no one acts).
PM approves (or uses Mentees > Assign Mentor(s), or Relationships > Add New Anchor Mentoring); the relationship appears under Relationships as Ongoing and notification mails go to both sides.
Meeting is booked by the mentee in the mentor's slots, or by PM via Meetings > Schedule a Meeting; it shows on both calendars.
After the call, mentor and mentee fill feedback forms; PM chases with Send Feedback Reminder and exports from Feedbacks.
PM reads completed / upcoming / cancelled counts in Analytics for the pipeline.

Example. AgroSense (fictional), a precision-irrigation startup in AGRI UDAAN, asks for help with export compliance; the PM matches it to an export consultant (fictional), a 45-minute call is held on 16 October, the founder rates it 5/5 and the mentor records 'apply for IEC and APEDA registration'. (At a-IDEA none of this has ever been done in Accubate: 0 relationships, 0 meetings.)

Programme Manager

One-off expert clinic

Relationships > Add a One-Time Meeting (only if 'One Time Mentorings' is switched on for the pipeline).
Pick mentor and startup, set the slot; the meeting appears under Meetings > Upcoming.
Mark complete; feedback follows.

Example. A visiting FSSAI expert (fictional) gives three 30-minute clinics to three startups in one afternoon.

Programme Manager, Founders

Run a learning session with QR attendance

Learning > Sessions > Add New: title, date, time, duration, virtual or physical, cover image.
Update Visibility: choose the pipelines whose managers can manage it; Update Speakers.
Attendees > Update Attendees; Send Calendar Invite; Send Announcement for reminders.
Settings: QR attendance on (with attendance form), optional external attendees, optional feedback form.
On the day: show or download the QR; attendees scan; Attendees tab shows Present / Absent.
Upload the recording and slides under Videos / Documents; Send Feedback Reminder; read Feedbacks.

Example. 'Export compliance for agri startups' (fictional), 90 minutes, virtual, for AGRI UDAAN 8.0 and KRISHIBOOT cohorts: 34 present, recording uploaded, average rating 4.4/5. (Only a 'Test Session' exists at a-IDEA.)

Mentor (or PM on the mentor's behalf)

Mentor manages own availability

Open Availability: set duration, buffer, booking buffer, timezone.
Add weekly hours per weekday; add date-specific overrides.
Slots appear for the next month for bookings.

Example. A mentor (fictional) offers Thursdays 15:00-18:00 and blocks a conference week.

Screens 25

Configure mentoring per pipeline/app/setup/builder/pipelines/list/<pipelineId>?section=Mentoring

Pipeline builder: Mentoring settings

The pipeline builder's Mentoring tab (reached from Mentoring > Settings) holds every mentoring rule for one pipeline as toggles. In the pipeline shown, Anchor Mentorings and Hide Details are on; Raise Mentor Connect Request, View All Mentors, One Time Mentorings, both feedback forms, General Feedback, Show Mentor Feedback to Mentee, Allow Mentors to Create Relationship and Show Startups to Mentor are off. The anchor-mentoring block (partly over-blurred by the privacy tool, but readable in the page text) sets the approval process (create the relation on apply, or send for Admin/Mentor approval), restrictions (max 5 active relations per mentee; auto-reject unapproved requests after 7 days), an application form, extras (mentor may create milestones / schedule meetings), six notification mail templates and whether a mentee may book meetings with the anchor mentor.

On screen: Raise Mentor Connect Request, View All Mentors (else recommended only), Anchor Mentorings: Approval Process, Restriction(s) (max 5 active relations, auto-reject after 7 days), Form(s), Additional(s) (mentor milestones, mentor schedules meetings), Email(s) x6 templates, Meeting Request, One Time Mentorings, Mentee's Feedback, Mentor's Feedback, General Feedback, Show Mentor Feedback(s) to Mentee, Allow Mentors to Create Relationship, Show Startups to Mentor, Hide Details (Team Members, Company Profile fields, Portfolio fields, General Documentation fields), Hide Startup Details from Administrators, left rail of module toggles: Active, Documentation, Canvas Model, IPRs (Patents, Copyrights, Trademarks, Publications), Market Access, Awards, Documents, Portfolio Management

Actions available: toggle each rule (auto-saves: 'Saved' under the title), Back, other builder tabs: Onboarding, Application/Portfolio/Company Profile, Documentation, Updates, Evaluation, Resource, Settings

Use case. The incubator admin sets, once per intake pipeline, how mentoring works: who may ask for a mentor, whether approval is needed, what mentors may see.

Example. Before AGRI UDAAN's next cohort, the admin switches on 'Raise Mentor Connect Request' and 'Mentee's Feedback' so that AgroSense (fictional) can ask for an export-compliance mentor and rate each session.

Build the mentor pool/app/setup/profiles/mentors

Setup > Directory > Mentors

The admin directory of non-startup profiles, with tabs for Mentors, Investors, Evaluators, Program Managers, Cohort Managers, Portfolio Managers and Evaluation Managers, plus Filters and Search. The Mentors list never loaded: its read call was blocked by the capture tool and the page shows a spinner and a 'Please check your network connection' toast.

On screen: tabs: Mentors, Investors, Evaluators, Program Managers, Cohort Managers, Portfolio Managers, Evaluation Managers, Filters, Search

Actions available: (list did not load)

Use case. Admin keeps one registry of mentors, investors and evaluators that pipelines draw from.

Example. The admin would add 'Dr. Meera Rao (fictional), export-compliance consultant' here before attaching her to a pipeline.

Build the mentor pool/ext/profiles/mentors

Public mentor directory

A public (outside the app shell) page listing every mentor in the directory, with Filters, Search and Grid / Table / List views. At a-IDEA it shows 'No mentors available'. It is linked from the app's Directory menu ('Mentor Directory: Every mentor listed in the public directory').

On screen: Filters, Search, Grid View, Table View, List View

Actions available: switch view, search, filter

Use case. Startups and the public browse available mentors.

Example. A founder from AgroSense (fictional) would browse here for mentors tagged 'exports' before raising a request.

Create relationships/app/mentoring/manage/list

Mentoring > Relationships

Landing tab of Mentoring for the selected pipeline (here AGRI UDAAN 8.0 Startups). Lists mentor-mentee relationships with status filter chips All / Ongoing / Cancelled / Completed (all 0) and a 'No mentorings' empty state. Tab bar: Relationships, Meetings, Mentors, Mentees, Feedbacks, Analytics, Requests.

On screen: pipeline title + Change Pipeline, filters: All, Ongoing, Cancelled, Completed (counts), Reset

Actions available: Settings (opens the pipeline builder's Mentoring section), Add New Anchor Mentoring, Add a One-Time Meeting

Use case. The Programme Manager sees every mentoring relationship in one intake and creates new ones.

Example. The PM pairs AgroSense (fictional) with an export-compliance mentor as an anchor mentoring for six months.

Pick the pipeline/app/mentoring (modal)

Change Pipeline selector

A searchable pop-up listing every pipeline grouped by programme (green header rows, type 'Incubation'), with Status (All / Active / Inactive) and Type (All / Application / Startup) chips. About 82 pipelines across 22 programmes (KRISHIBOOT alone has 18). All Mentoring tabs, and their counts, depend on this choice.

On screen: Search, Status: All, Active, Inactive, Type: All, Application, Startup, programme group rows with type, pipeline rows

Actions available: select a pipeline

Use case. The PM must switch context to the right intake before doing any mentoring work.

Example. To check NABARD CCF 4.0 startups' mentoring, the PM searches 'NABARD' and picks 'NABARD CCF Investment Support 4.0 Startups'.

Add mentors to the pipeline/app/mentoring/manage/mentors

Mentoring > Mentors

Mentors attached to this pipeline with three summary cards (Mentor(s) Used, Unique Relation(s) Created split Anchor / One Time, Total Meeting(s) split Upcoming / Completed) and a sortable table. AGRI UDAAN 8.0 has exactly one mentor (an a-IDEA staff member) with 0 relations, 0 requests and 0 meetings; every other pipeline checked shows 'No mentors available'.

On screen: Mentor(s) Used, Unique Relation(s) Created (Anchor, One Time), Total Meeting(s) (Upcoming, Completed), columns: Name, Email, Unique Relation(s), Requests, Meetings, Actions, View 20 per page

Actions available: Add Mentor, Filters, Search, row options menu

Use case. PM sees which mentors are active in an intake and how much each is used.

Example. The PM spots that the export-compliance mentor has 4 anchor relations and 11 completed meetings this year (fictional).

Set mentor availability/app/mentoring/manage/mentors (menu)

Mentor row options

The row's three-dot menu offers only two items: Booking Window and Availability. There is no 'view profile' or 'edit expertise' item; the mentor's name is not a link.

On screen: Booking Window, Availability

Actions available: Booking Window, Availability

Use case. PM manages when a mentor can be booked, on the mentor's behalf.

Example. The PM opens Availability for a visiting mentor who is only free on Thursday afternoons (fictional).

Set mentor availability/app/mentoring/manage/mentors (full-screen panel)

Mentor availability (slot set-up)

Full-screen panel for one mentor (name masked). Header settings: Duration 45 min, Interval/Buffer 5 min, Booking Buffer 1 hour, Timezone Asia/Calcutta. Left: Weekly Schedule, Sunday to Saturday, each 'Unavailable' with + to add hours ('slots will appear every week for next 1 month'). Right: 'Schedules for particular date(s)' that override the weekly hours. The separate 'Booking Window' dialog ('Open For: <programme>') did not load: its slots call was blocked.

On screen: Duration (in min), Interval/Buffer Time (in min), Booking Buffer Time (in hour), Timezone, Weekly Schedule per weekday, Schedules for particular date(s)

Actions available: edit duration/buffers (pencil), + add hours per day, Add New / Add schedules for specific dates, close

Use case. Mentor or PM publishes bookable slots so that mentees can book meetings without e-mail ping-pong.

Example. The export-compliance mentor (fictional) opens Thursdays 15:00-18:00 with 45-minute slots and a 5-minute gap, and blocks 2 October for a holiday.

See the pipeline's mentees/app/mentoring/manage/mentees

Mentoring > Mentees

Every startup in the pipeline listed as a potential mentee (15 for AGRI UDAAN 8.0, all Active) with cards Mentee(s) Benefitted (0), Unique Relation(s) Created, Total Meeting(s), and a table with checkboxes for bulk actions. Startup and founder cells are blurred.

On screen: Mentee(s) Benefitted, Unique Relation(s) Created, Total Meeting(s), columns: Startup Id (AIDE-Sxxxxx) + status, Startup, Name, Email, Unique Relation(s), Requested Mentorings, All Meetings, row checkboxes

Actions available: Assign Mentor(s), Send Announcement, Export to Excel, Filters, Search Mentees

Use case. PM finds startups that have no mentor yet and bulk-assigns mentors or announces mentor office hours.

Example. The PM ticks AgroSense (fictional) and two other startups with 0 relations and uses 'Assign Mentor(s)' to give them the export mentor.

Receive mentor-connect requests/app/mentoring/manage/requests

Mentoring > Requests

Inbox of mentor-connect requests raised by startups awaiting admin/mentor approval. Shows only 'No new request(s) received' (the pipeline has request-raising switched off).

On screen: request list (empty)

Actions available: (approve / reject on each request, per settings; none visible)

Use case. PM or mentor approves or rejects startups' requests to connect; unapproved requests auto-reject after the configured days.

Example. AgroSense (fictional) asks for 'help with APEDA export registration'; the PM approves and the relationship is created.

Schedule and hold meetings/app/mentoring/manage/meetings

Mentoring > Meetings

All mentor meetings in the pipeline with status chips All / Upcoming / Requested / Completed / Cancelled and a 'No meetings found' empty state.

On screen: filters: All, Upcoming, Requested, Completed, Cancelled, Reset

Actions available: Schedule a Meeting, Import, Download

Use case. PM schedules or imports past meetings and checks what is coming up.

Example. The PM schedules a 45-minute call on 16 October between AgroSense (fictional) and its mentor, then marks it completed afterwards.

Collect feedback/app/mentoring/manage/feedbacks

Mentoring > Feedbacks

Feedback submitted after meetings, filterable All / Mentor Feedback / Mentee Feedback. Empty ('No feedbacks received').

On screen: filters: All, Mentor Feedback, Mentee Feedback

Actions available: Settings, Send Feedback Reminder, Export to Excel

Use case. PM checks session quality and chases missing feedback.

Example. After the 16 October call, the founder rates it 5/5 and the mentor notes 'register with APEDA; prepare FSSAI documents' (fictional).

Track mentoring/app/mentoring/manage/analytics

Mentoring > Analytics

Three cards (Upcoming Meetings and Completed Meetings, each split Anchor / One Time; Cancelled Meetings) and a year picker (2026) above a meetings chart area that shows 'No meetings found'. Analytics are per pipeline only.

On screen: Upcoming Meetings, Completed Meetings, Cancelled Meetings, year selector

Actions available: change year

Use case. PM or head of incubation reports mentoring activity to a funder.

Example. For the NIDHI report the PM would read '42 completed mentor meetings in 2026' (fictional) from here, but would have to repeat this for each pipeline.

Run events/app/events

Events

'Manage your event(s)' list with Add filter and Search Events; a-IDEA has no events ('No events found'). Event detail, registration/RSVP and attendance screens could therefore not be seen, and there is no public events page (/ext/events returns 404).

On screen: Search Events, Add filter

Actions available: Add New, Add filter

Use case. PM would publish demo days, workshops or meet-ups and track registrations.

Example. a-IDEA would create 'Agri Demo Day, 20 Nov' (fictional) here; today it runs such events outside Accubate.

Run learning/app/learning

Learning home

Learning resources 'organised by mode of delivery': Scheduled delivery (Sessions: 'scheduled sessions, attendance and recordings', 0 upcoming), Self-paced study (Courses: 'modules, lectures and assignments', 0 courses) and Reference material (Library: 'curated material shared with cohorts', 0 items). Each card can be starred into a PINNED strip (none pinned).

On screen: PINNED, Sessions (count upcoming), Courses (count), Library (count items)

Actions available: open a card, star / pin a card

Use case. PM or founder enters the learning area and picks a delivery mode.

Example. A founder opens Sessions to find the 'Export documentation masterclass' (fictional).

Run learning: sessions/app/learning/session/list

Learning > Sessions

List of sessions as cards with a cover image, title, mode (Virtual), date, time, duration and a status pill. Only one exists: 'Test Session', Virtual, 24 Jul 2026, 10:00 AM, 1 hr, Completed.

On screen: cover image, title, Virtual/Physical, date, time, duration, status (Completed)

Actions available: Add New, Filters, Search Sessions, open session

Use case. PM schedules lectures and workshops for cohorts; founders see what is coming.

Example. The PM schedules 'Export compliance for agri startups' (fictional), virtual, 90 minutes, for AGRI UDAAN 8.0 and KRISHIBOOT cohorts.

Run learning: sessions/app/learning/session/list/<id>

Session detail: Home

Session page with tabs Home, Attendees, Announcements, Feedbacks. Home has a media area (Videos / Images / Documents with Upload) for recordings and slides, likes and comments, and a right column with Timings (date and time, duration, type, location), 'Share QR for attendance' with a QR code and Download QR, Speakers (0) with Update Speakers, and Update Visibility listing the five pipelines whose admins and programme/cohort managers can manage it. Media and comments did not load (blocked reads).

On screen: Videos / Images / Documents, Likes, Comments, Date & Time, Duration, Type, Location, Share QR for attendance, Speakers, Visibility pipelines

Actions available: Settings, Send Announcement, Edit, Delete, Send Calendar Invite, Send Feedback Reminder, Upload, Download QR, Update Speakers, Update Visibility, comment + Send

Use case. PM runs a session end to end: invite, take attendance by QR, upload the recording, collect feedback.

Example. At the masterclass the PM projects the QR; 34 founders scan it to mark attendance and the recording is uploaded under Videos (fictional).

Run learning: sessions/app/learning/session/list/<id> (Attendees tab)

Session detail: Attendees

Attendee list with filters All / Present / Absent and Search; empty ('No attendees'), possibly because the attendee read call was blocked.

On screen: filters: All, Present, Absent, Search

Actions available: Settings, Send Announcement, Update Attendees, Remove Attendees, Download, Send Calendar Invite, Send Feedback Reminder

Use case. PM picks who is invited and checks who actually attended.

Example. The PM filters 'Absent' to send the recording link to the 6 founders who missed the session (fictional).

Run learning: sessions/app/learning/session/list/<id> (Announcements tab)

Session detail: Announcements

History of announcements sent to the session's attendees ('No communications added.').

On screen: communications list

Actions available: Settings, Send Announcement

Use case. PM sends reminders or changes (venue, link) to attendees and keeps a record.

Example. 'Zoom link changed; join 5 minutes early' sent to all attendees the morning of the session (fictional).

Run learning: sessions/app/learning/session/list/<id> (Feedbacks tab)

Session detail: Feedbacks

Feedback received from attendees after the session ('No feedbacks received').

On screen: feedback list

Actions available: Settings, Send Feedback Reminder

Use case. PM measures session quality for programme reports.

Example. Average 4.4/5 from 28 responses; 'more case studies' is the top comment (fictional).

Run learning: sessions/app/learning/session/list/<id> (Settings modal)

Session settings

Modal with three switches: take attendance using QR (on, with 'Default Attendance Form' and Edit / Change), collect attendance of external users (those not marked as attendees; off), and attach a feedback form (off).

On screen: QR attendance + attendance form, external user attendance, attach feedback form

Actions available: toggle switches, Edit / Change attendance form, close

Use case. PM decides how attendance and feedback are captured for one session.

Example. For an open workshop the PM allows external attendees so that walk-in FPO members can scan the QR too (fictional).

Run learning: courses/app/learning/course

Learning > Courses

Self-paced course list with filters All / Ongoing / Upcoming / Completed and search; empty ('No courses found'). Course, module and lecture screens could not be seen.

On screen: filters: All, Ongoing, Upcoming, Completed, Search Courses

Actions available: Add New

Use case. PM builds structured courses (modules, lectures, assignments) that founders work through.

Example. A 6-module 'Agri export readiness' course with a quiz per module (fictional).

Run learning: reference library/app/learning/library

Learning > Library

Digital library of files shared with cohorts; empty ('No files uploaded'), with an 'Add New' drop-down (not opened).

On screen: file list

Actions available: Add New (drop-down)

Use case. PM shares templates and reading material that founders consult when needed.

Example. The PM uploads a 'DGFT IEC application checklist' PDF for all agri cohorts (fictional).

See everything on the calendar/app/user/calendar

My calendar: month view

Personal calendar (user name masked) with previous / Today / next and a Day / Week / Month / Agenda view switch. July 2026 shows the single learning session on 24 July at 10:00 AM (its chip is blurred by the tool). October 2026 is empty.

On screen: month grid, event chips (title, time), view: Day, Week, Month, Agenda

Actions available: previous / next, Today, switch view

Use case. Any user (PM, mentor, founder) sees their sessions and mentor meetings in one place.

Example. The AgroSense founder (fictional) sees the 16 October mentor call and the 20 October masterclass side by side.

See everything on the calendar/app/user/calendar (Agenda)

My calendar: agenda (list) view

Agenda view: a compact month picker on the left and 'Schedule for <day>' on the right listing that day's items (empty for 12 October 2026). This is the closest thing to a list view.

On screen: mini month, Schedule for selected day

Actions available: pick a day, previous / next, switch view

Use case. Quick daily agenda for a mentor or PM.

Example. A mentor (fictional) checks today's three 45-minute calls.

Facts observed

Mentoring is scoped per pipeline: about 82 pipelines across 22 programmes appear in the Change Pipeline selector (KRISHIBOOT has 18, AGRI UDAAN and NABARD CCF 8 each), filterable by Status (Active/Inactive) and Type (Application/Startup).
Across 20 startup pipelines checked (AGRI UDAAN 5.0-8.0, KRISHIBOOT, NABARD CCF 1.0-4.0, NIDHI SSS, BIRAC SEED FUND, MEITY SAMRIDH 2.0, ABI, a-IDEA Incubation, the 2022 incubatee lists): 0 mentoring relationships, 0 meetings, 0 requests, 0 feedbacks.
Only AGRI UDAAN 8.0 Startups has a mentor attached: one (an a-IDEA staff member), with 0 relations; that pipeline lists 15 active startups as mentees.
The public mentor directory (/ext/profiles/mentors) shows 'No mentors available'; Setup > Directory groups 7 profile types (Mentors, Investors, Evaluators, Program Managers, Cohort Managers, Portfolio Managers, Evaluation Managers); the Setup card says '10 profiles' in total.
Mentoring settings defaults seen: max 5 active mentoring relations per mentee; unapproved requests auto-rejected after 7 days; six notification templates (request received, approval, rejection, expiry, mentoring assigned to mentee, mentoring assigned to mentor).
Two mentoring types: Anchor (long-term mentor assigned to a mentee) and One Time (a single meeting for a specific problem).
Mentor availability defaults: 45-minute slots, 5-minute buffer, 1-hour booking buffer, Asia/Calcutta timezone; the weekly schedule repeats for the next 1 month; date-specific overrides are supported.
Mentor startup-data visibility can be limited per pipeline: hide Team Members and selected Company Profile, Portfolio and General Documentation fields, optionally from administrators too.
Events: 0 events; no public event page exists (/ext/events is 404).
Learning has three delivery modes: Sessions (scheduled, with attendance and recordings), Courses (self-paced modules, lectures, assignments), Library (reference files). Counts at a-IDEA: 1 session ('Test Session', 24 Jul 2026, virtual, 1 hr, completed, 0 attendees, 0 speakers), 0 courses, 0 library files.
Sessions offer QR attendance with an attendance form, external-attendee capture, an optional feedback form, calendar invites, announcements, a media area (videos, images, documents), likes and comments, and visibility by pipeline (the test session is shared with 5 pipelines).
No 'certificates' screen exists under Learning or in the menu. Tools > Documents ('documents collected from and issued to members', 25) may be where certificates would be issued; not explored here (Tools area).
Tools > Resources holds 4 partner perks (2 cloud-credit offers, 1 insurance, 1 payments), with Subscriptions, Summary and Analytics tabs. These are perks, not learning content.
User calendar: Day / Week / Month / Agenda views; it showed the July test session; October 2026 was empty.

Strengths

Thorough per-programme rule set for mentoring (approval flow, relation limits, auto-expiry, request forms, milestones, who may schedule, who sees which startup fields).
Clear split between anchor (long-term) and one-time mentoring.
Self-service mentor availability with buffers, booking lead time, timezone and date overrides, Calendly style.
Two-way feedback (mentor and mentee) with reminders and Excel export.
Sessions cover the whole flow: calendar invite, announcements, QR attendance (including walk-ins), recording upload, feedback.
Bulk actions on mentees (assign mentors, announce, export).
Learning home explains the three delivery modes in plain language, with pinning.

Gaps and friction

Not used at a-IDEA: 0 relationships, 0 meetings, 0 events, 0 courses, 0 library files, 1 test session. a-IDEA's mentoring, events and training run outside Accubate.
Everything is per pipeline. A mentor must be added pipeline by pipeline, analytics cannot be rolled up across programmes, and the PM must work through about 82 pipelines with 'Change Pipeline'.
The mentor list shows only name and email: no expertise, sector, rating or capacity, and the name opens no profile. There is no matching or suggestion of mentors for a startup's need.
No honorarium or mentor-payment tracking, and no session notes or action items visible in Mentoring (only feedback forms).
Empty states give no guidance (for example, Requests just says 'No new request(s) received' even when requests are switched off).
Settings live in the pipeline builder and auto-save on toggle: easy to change by accident, with no confirmation.
Events cannot be evaluated (none exist) and there is no public event or RSVP page.
No certificates for learning; no visible link between sessions and mentoring.
Several screens make many legacy API calls (api-legacy.accubate.app) and show a generic 'check your network connection' toast when one fails.

For INQB Zone

Low adoption is the main finding. a-IDEA has no mentoring, event or learning data to migrate from Accubate, so INQB Zone competes with spreadsheets and WhatsApp here, not with Accubate data. Make these modules lightweight and PM-led (as decided: founders request, the PM books every session).
Keep one mentor profile across centres and programmes (as decided), with expertise tags, sectors, languages, capacity and ratings. Attach mentors to a centre, not to each intake pipeline, and filter by programme instead of switching pipeline.
Copy the availability model: slot length, buffer, booking lead time, weekly hours plus date overrides. India-only timezone default.
Copy the anchor vs one-time distinction, but with sensible defaults. Expose 4-5 settings, not 15 toggles, and confirm changes rather than auto-saving.
Add what Accubate lacks: session notes and action items, mentor-need matching (AI can suggest mentors from the founder's request text; the PM confirms), the monthly honorarium claim, and cross-programme mentoring analytics for funder reports.
Keep mentor feedback and mentee ratings two-way, with reminders and per-mentor averages; per MoU and decisions, never show evaluator or mentor ratings of startups to other startups.
For events, the v1 RSVP plugin (founder's Q11) should have a public event page, RSVP, QR check-in (copy Accubate's session QR) and the attendance list, which Accubate's a-IDEA instance does not use.
For learning, sessions with QR attendance, recording and feedback matter more than self-paced courses. Fold the 'library' into resources. Consider attendance-based certificates (generated PDF), which Accubate does not offer.
Give every mentor meeting and session one personal calendar with an agenda view, and offer ICS export (busy-time reads are allowed under MoU v0.7 E5).

Funding, communication and admin tools

This part of Accubate holds the incubator's back-office tools: outbound communication (system mail templates, email announcements with delivery tracking, a noticeboard), information requests (surveys) and support (a grievance ticket desk), the funding module (grant, equity and debt funds, nominations, recipients and tranches), financial administration (invoices, accounting, payment accounts), partner perks, documents, certificates, a reports generator and site-usage audit logs, plus each user's personal tools (tasks, inbox, chat, notifications, search, account menu). At a-IDEA the communication and grievance tools are used heavily (569 email announcements, mostly round results; 74 grievance tickets, 53 still open), while funding, invoices, accounting, payments, tasks, inbox, chat and the reports generator are empty or unused. Funding is meant to run after selection and onboarding (nominate a startup to a fund, move it through stages, release tranches against milestones), but a-IDEA holds no fund records; only one test-like nomination and one orphaned recipient exist.

Set up system mail templates
Broadcast announcements and notices
Track email delivery
Collect information through surveys
Raise and resolve grievances
Create a fund and nominate startups
Release tranches and track milestones
Invoice, account and take payments
Offer partner perks (resources)
Map applications to startup records
Store documents and issue certificates
Report and audit usage
Personal workspace: tasks, inbox, notifications, search, account

Use cases

Fund manager / accounts team

Accounts team records a ₹5 L seed tranche for AgroSense (fictional)

Funding > Grant Funds > Add New Funding: create 'Seed Fund 2026' with corpus and call window
Nominate AgroSense to the fund; move the nomination through stages (Demote / Reject / Move to next stage) to Onboarded
AgroSense appears in All Recipients; open it to see allocated, disbursed, expenditure and milestones
Edit Total Allocated Amount to ₹5,00,000, then Initiate next tranche once milestone 1 is completed
Export to Excel for the funder's utilisation report

Example. Not used at a-IDEA: no fund records exist, so in practice seed-fund tranches are tracked outside Accubate.

Programme Manager

PM sends a monthly-report reminder announcement

Tools > Announcement > Send New (email only)
Choose recipients (cohort or startups), write the subject and use {{User Name}} in the body
Send, then open the row menu > View Report to check delivered, opened and clicked
Use Resend Content for anyone who did not open it
Optionally rely on the system 'Startup Update Reminder' template instead (duplicate it to customise)

Example. The PM emails all AgriSpark 3.0 (fictional) incubatees on the 1st: 'Monthly health report due by the 5th'; the report shows 38 of 40 opened.

Programme Manager

Announce round results to applicants

After evaluation, select the shortlisted (or rejected) applicants
Send Announcement with a congratulation or regret template
Check the delivery report

Example. This is the most common real use at a-IDEA: most of the 569 announcements are round outcomes for KrishiBoot, AGRI UDAAN, ABI incubation and NABARD CCF calls.

Founder or applicant, then programme staff

Founder raises a grievance and staff resolve it

Founder uses the Support link > Report an Issue: title, type (Program Related or Platform Related Tech Support), details, optional file
Ticket appears under Tools > Grievances, assigned to every staff member configured (about 20 people)
A staff member clicks Assign to Me, opens View, acts outside the tool (no reply box) and clicks Close Ticket
Analytics shows open versus closed counts

Example. AgroSense (fictional) reports that the deck upload fails an hour before the deadline; the associate reopens form access and closes the ticket.

Programme Manager, then founders

Collect pitch-book information with a survey

Tools > Survey > Add New; choose the form template and toggles (multiple responses, emails, payment, evaluation)
Form Header Design: add poster and description, copy the public link or QR
Share the link; founders fill the numbered form
Responses tab: export, or 'Onboard As' to create startup records

Example. Before Demo Day the PM collects one-liners and milestones from 25 incubatees, then exports them into the pitch book.

Admin / data protection lead

Audit who downloaded applicant data

Setup > Site Usage > Download Logs
Search by user or pipeline; read flow, type and time

Example. The admin checks which staff exported the AgriSpark 3.0 (fictional) applicant list as Excel this week.

Screens 35

Entry point/app/tools

Tools hub

A card hub grouped into Outbound communication (Announcement, Noticeboard), Requests and resolution (Survey, Grievances), Records and documents (Documents, Resources, Mappings) and Financial administration (Accounting, Invoices). Each card shows a live count and can be pinned with a star; a 'Recently visited' strip sits at the top.

On screen: Pinned, Recently visited, Announcement: 569 announcements, Noticeboard: 1 notice, Survey: 2 surveys, Grievances: 53 open, Documents: 25,819 files, Resources: 4, Mappings: 26, Accounting: 0 accounts, Invoices: 0 this quarter

Actions available: Open a tool, Pin a tool (star)

Use case. Programme Managers and admins reach every back-office tool from here.

Example. A Programme Manager pins Announcement and Grievances so they appear first every morning.

Set up system mail templates/app/setup/builder/mail

Mail templates (system emails)

List of 298 email templates (the Setup hub says 256) behind every automated mail, with category, creator and status. Vendor-made defaults carry a lock icon; categories seen include Mentoring, MentorRequest, Application, Funding, Payment, Grievance, Investment, Invoice, Announcement, Session, On-Boarding and Updates Reminder. Subjects use merge tags such as {{Sid}}.

On screen: Title, Last Modified, Created At, Category, Created By, Status (PUBLISHED), Actions

Actions available: Add New, Add filter, Search Mail, Edit, Duplicate, Delete (disabled on locked defaults)

Use case. An admin changes the wording of the emails the system sends at each step (reminders, invites, receipts).

Example. The admin duplicates 'Startup Update Reminder' to add a-IDEA's monthly-report deadline before the 5th.

Set up system mail templates/app/setup/builder/mail/1000000024

Mail template view (locked default)

Opening the system 'Startup Update Reminder' shows its subject '{{Sid}} Reminder for Update' and body with merge tags ({{User Name}}, {{Updates Title}}, site name), plus a red note that default system templates cannot be edited and must be duplicated. Body text is over-blurred in the capture because it contains the merge tag {{User Name}}.

On screen: Subject, Body with merge tags, Lock notice

Actions available: Close

Use case. Admins check what a system email says before relying on it.

Example. The PM confirms the update reminder links startups to the Updates section before switching it on for a cohort.

Broadcast announcements and notices/app/tools/announcements

Announcements list

Paged list of 569 broadcasts (20 per page). Every one visible is Type 'Email'; most are round outcomes ('Congratulations - Selected for the Final round of ...', 'Outcome - Round 1 - AGRI UDAAN 8.0', 'Rejection Mail of ABI Incubation 4.0', NABARD CCF outcomes) and screening links. Recipient count per announcement is shown (1 to 133; blurred in capture).

On screen: Subject, Type (Email), Created At, Recipient(s) count, Actions menu

Actions available: Send New, Filters, Search Announcement, Row menu: Resend Content, View Report, Click subject to view

Use case. Programme Managers email results and instructions to applicants and startups after each evaluation round.

Example. A PM sends 'Selected for Final round of AgriSpark 3.0 (fictional)' to 40 shortlisted applicants with the pitch-day date.

Broadcast announcements and notices/app/tools/announcements (modal)

View announcement

Modal showing To (n Recipient(s) with every name and email listed inline), Cc, Bcc, Subject and the HTML body. Bodies start with the merge tag {{User Name}}; this example tells shortlisted applicants the final-round dates, asks them to upload their deck and financials on the portal, and gives a staff contact with email and mobile number. Recipient list, salutation and contact line are blurred in the capture.

On screen: To (count + list), Cc, Bcc, Subject, Body

Actions available: Close

Use case. Staff check exactly what went to whom.

Example. A PM re-reads the final-round email to confirm the date sent to AgroSense (fictional).

Track email delivery/app/tools/announcements (View Report modal)

Announcement delivery report

Per-announcement tracking: Total Delivery, Total Opened and Total Clicked as counts and percentages (example: 46/46 delivered, 46/46 opened, 0/46 clicked), then one row per recipient with status (Sent) and Delivered/Opened/Clicked/Bounced timestamps. Many cells read 'Data Not Captured'.

On screen: All / Sent filter, Search User, Total Delivery, Total Opened, Total Clicked, Recipient, Status, Delivered At, Opened At, Clicked At, Bounced At

Actions available: Download, Filters, Reset

Use case. A PM checks whether a screening link reached every applicant before a deadline.

Example. The PM sees that 3 of 46 applicants never opened the 3rd-round link and phones them.

Broadcast announcements and notices/app/tools/noticeboard

Noticeboard

One notice card: title, a tag ('Incubation'), a URL (a YouTube video) and an empty description, with an Active toggle, edit and delete icons.

On screen: Title, Tag, URL, Description, Active

Actions available: Add New, Active toggle, Edit, Delete

Use case. Admins pin a standing notice or video for everyone who logs in.

Example. a-IDEA pins a 'How to file your monthly update' video for all incubatees.

Collect information through surveys/app/tools/survey

Survey list

Only 2 surveys exist, created in Dec 2021 and Aug 2022, both 'last modified' on the same day in Nov 2024 (a migration date) and both with 0 responses. Columns include a category (Feedback, Others).

On screen: Title, Created Date, Last Modified, Category, Responses, Actions

Actions available: Add New, Add filter, Search Survey, Edit, Delete

Use case. PMs build one-off forms (feedback, information requests) outside the application pipeline.

Example. The PM creates 'Pitch-book details 2026' to collect a one-liner and milestones from each incubatee.

Collect information through surveys/app/tools/survey/list/20

Survey settings

Survey record with tabs Settings, Form Header Design, Responses, Analytics and Managers. Settings are toggles: survey active, survey form template (Change), allow multiple responses per email, respondent email template, managers' email on each submission, enable payment after submission, enable evaluation of responses.

On screen: Is the survey active?, Survey Form Template, Allow Multiple Responses, Respondent Email Template, Managers Email Template, Enable Payment, Enable Evaluation

Actions available: Export to Excel, Print to PDF, Import, Send Announcement, Back

Use case. A PM decides who is notified, whether a fee is collected and whether responses are scored.

Example. For a paid workshop sign-up the PM turns on Enable Payment and the respondent confirmation email.

Collect information through surveys/app/tools/survey/list/20 (Form Header Design tab)

Survey form header design (public link)

Public application link (/ext/survey/20/apply) with QR code, copy-link icon and HTML embeddable code, plus rows for Background, Title, Poster, Description, Supporting Documents, Social Media icons, Post Submission Message, Redirect URL, Google Tag Manager and Facebook Pixel ID.

On screen: Application Link, Background, Title, Poster, Description, Supporting Documents, Social Media, Post Submission Message, Redirect Url, Google Tag Manager, Facebook Pixel ID

Actions available: Add New link, Add / Edit per row, QR code, Copy link

Use case. The PM brands the public form and gets a shareable link or QR for WhatsApp groups and posters.

Example. The PM adds an a-IDEA poster and redirects respondents to the cohort's event page after submitting.

Collect information through surveys/ext/survey/20/apply

Public survey form (respondent view)

What a respondent sees: a numbered 17-question form (Name, Email, Company overview, Business model, Products/services, Competitive advantage, IP, Achievements, Sector, Incorporation date, Founders, Advisors/mentors, Total investment, Website, One-liner, milestone document upload, mentoring expectations) with 'Max 50 words' hints and character counters. Name and email are typed again even by logged-in users; nothing is pre-filled from the startup profile.

On screen: Numbered questions, Required markers, Character counters, File upload, Submit

Actions available: Submit (not used), Upload your file (not used)

Use case. Founders answer an information request from the incubator.

Example. The founder of AgroSense (fictional) fills in the pitch-book form before Demo Day.

Collect information through surveys/app/tools/survey/list/20 (Responses tab)

Survey responses

Response grid toolbar: Export to Excel, Print to PDF, Import, Send Announcement, Edit Columns and 'Onboard As' (turn respondents into startup or user records), with filter and search. This survey has no responses, so the grid stays on a spinner; the Analytics tab says 'No analytics to display'.

On screen: Add filter, Search Responses, Edit Columns

Actions available: Export to Excel, Print to PDF, Import, Send Announcement, Onboard As

Use case. A PM reviews answers and can onboard respondents directly as startups.

Example. After a road-show survey, the PM onboards 12 respondents as pre-incubation startups.

Raise and resolve grievances/ext/grievance/register

Report an issue (raise a ticket)

Form behind the 'Support' footer link and the 'Raise a Ticket' button: Summary/Title, Type of Issue (Program Related or Platform Related Tech Support), detailed explanation (5,000 characters) and an optional supporting document.

On screen: Summary/Title, Type of Issue, Explain your problem in detail, Supporting Document

Actions available: Upload your file (not used), Submit (not used)

Use case. Founders and applicants report a problem with a programme or with the platform.

Example. The founder of AgroSense (fictional) reports that the pitch-deck upload fails on the final-round form.

Raise and resolve grievances/app/tools/grievance

Grievances list

Card list of tickets (53 open of 74; 21 closed) with status, title, ticket UUID, Assigned To, Raised By, Last Updated, Issue Type, Raised On and a summary. Most open tickets are applicants asking about results ('No update on application', 'when can we expect the result') or upload and edit problems before deadlines. Each 'Program Related' ticket is assigned to about 20 staff at once.

On screen: Status, Title, Ticket ID, Assigned To, Raised By, Last Updated, Issue Type, Raised On, Details Summary

Actions available: Raise a Ticket, Settings, Analytics, Filters: All / Open / Closed, Search, View, Close Ticket, Assign to Me

Use case. Staff work the support queue for applicants and incubatees.

Example. A programme associate opens 'unable to upload pitch deck', picks Assign to Me and fixes the form access.

Raise and resolve grievances/app/tools/grievance/<uuid>/view

Grievance detail

Ticket detail: Issue Id, Status, Issue Type, Raised On, Last Updated, Raised By, Assigned To and Details, with an activity timeline on the right (assigned, closed by). The example, an applicant asking why a NIDHI-PRAYAS application was rejected, was closed about 10 months after it was raised with no reply recorded in the thread. There is no reply box on the detail page.

On screen: Issue Id, Status, Issue Type, Issue Raised On, Last Updated, Issue Raised By, Assigned To, Details, Timeline

Actions available: Re-open Ticket, Back

Use case. Staff read the full complaint and its history before acting.

Example. The PM reads AgroSense's (fictional) rejection query and replies by email with the jury's summary.

Raise and resolve grievances/app/tools/grievance (Analytics modal)

Grievance analytics

Modal with Total Tickets (74) and two switchable charts (pie, bar or other): Status-wise (53 open, 21 closed) and Pipeline-wise (73 'General', 1 tied to a 2022 pipeline).

On screen: Total Tickets, Status-Wise Tickets, Pipeline-Wise Tickets

Actions available: Switch chart type, Close

Use case. The head of the incubator checks support load.

Example. The COO sees 53 open tickets and asks the team to clear those older than a week.

Raise and resolve grievances/app/tools/grievance (Settings modal, General)

Grievance settings: general escalation levels

General tab says 'No grievance setting' and offers 'Add new level'. No escalation levels are configured at a-IDEA.

On screen: General, Cohort Wise, Levels

Actions available: Add new level

Use case. An admin defines who handles tickets at each escalation level.

Example. Level 1 Programme Associate, Level 2 Programme Manager after 3 days, Level 3 COO after 7 days.

Raise and resolve grievances/app/tools/grievance (Settings modal, Cohort Wise)

Grievance settings: cohort-wise

Per-cohort routing: choose a cohort (ABI - Call for Incubation 2023), one assignee, the mail template the assignee receives and the one the issue creator receives (both 'No template selected').

On screen: Select Cohort, Assignee, Mail template to assignee(s), Mail template to issue creator

Actions available: Edit

Use case. Route tickets from one cohort to its own cohort manager.

Example. Tickets from the AgriSpark 3.0 (fictional) cohort go only to its cohort manager.

Create a fund and nominate startups/app/funding/grant

Funding: Grant Funds

Funding module with tabs Grant Funds, Equity Funds, Debt Funds, Demo Days ('Coming Soon'), All Nominations and All Recipients. KPI tiles: Total Amount, Open, Closed, Upcoming, Unique Sources. All three fund types are empty at a-IDEA ('No Funding Found').

On screen: Total Amount, Open, Closed, Upcoming, Unique Sources, Search

Actions available: Add New, Add New Funding

Use case. The fund manager records each grant scheme (for example a seed fund) with its corpus and call window.

Example. Accounts creates 'Seed Fund 2026' (fictional): ₹50 L corpus, grant type, call open 1 to 31 March.

Create a fund and nominate startups/app/funding/nominations

Funding: All Nominations

Table of nominations of startups to funds. Only one exists: status 'Onboarded', nominated by the vendor's support account in April 2024; its Funding Id column is empty. Opening it (/app/funding/detail/34/nominations/view/911) shows Print, Export to Excel, Demote, Reject and 'Move to next stage' (so nominations run through stages like an application pipeline), but the page never finished loading because a read call was blocked.

On screen: Nomination Id, Funding Id, Status, Nominated By, Nominated At

Actions available: Open nomination: Print, Export to Excel, Demote, Reject, Move to next stage

Use case. A PM nominates a selected startup to a fund and moves the nomination through due-diligence stages.

Example. The PM nominates AgroSense (fictional) to Seed Fund 2026; the committee moves it to 'Onboarded'.

Release tranches and track milestones/app/funding/recipients

Funding: All Recipients

Recipients table with Recipient Id, recipient, name, email, Funding, Fund Allocated, Fund Disbursed, 'Tranche started on' and a Journey icon. The single row has no name, funding or allocation but ₹250,000.00 disbursed, and its 'Tranche started on' shows the current clock time (looks like an empty date). Its link points to /app/funding/detail/undefined/... (a front-end bug).

On screen: Recipient Id, Recipient, Recipient Name, Email, Funding, Fund Allocated, Fund Disbursed, Tranche started on, Journey

Actions available: Send Announcement, Export to Excel, Filters, Search Recipients, Row checkbox

Use case. Accounts and PMs see every funded startup and how much has gone out.

Example. Accounts filters recipients of Seed Fund 2026 (fictional) to see ₹5 L allocated and ₹2 L released to AgroSense.

Release tranches and track milestones/app/funding/detail/34/recipients/view/123

Recipient tranche dashboard

Per-recipient view with tiles Funding, Total Disbursed Amount, Total Allocated Amount (Edit), Total Expenditure, Milestones, Active Milestones and Completed Milestones, and actions to print, export, delete a tranche or 'Initiate next tranche'. At a-IDEA it loads empty (the parent fund record no longer exists).

On screen: Funding, Total Disbursed Amount, Total Allocated Amount, Total Expenditure, Milestones, Active Milestones, Completed Milestones

Actions available: Back, Print, Export to Excel, Delete Tranche, Initiate next tranche, Edit allocation

Use case. Finance releases the next tranche once milestones are met and expenditure is reported.

Example. Accounts records the ₹5 L seed tranche for AgroSense (fictional) after milestone 1 (pilot with 50 farmers) is marked complete.

Invoice, account and take payments/app/tools/invoices

Invoices

Invoices tool with Invoices and Analytics tabs and actions Add New, Manage Verifications, Print, Send and Delete. Empty ('No Invoice available'); Analytics shows 'No invoices for this year'. Accounting (/app/tools/accounting, with Accounts and Counter Parties tabs) and Setup > Payments (payment accounts) are also empty.

On screen: Invoices, Analytics

Actions available: Add New, Manage Verifications, Print, Send, Delete, Add Invoice

Use case. The accounts team raises incubation-fee or service invoices to startups.

Example. Accounts raises a ₹15,000 + GST quarterly incubation-fee invoice to AgroSense (fictional).

Offer partner perks (resources)/app/tools/resources

Resources (partner perks)

Perk catalogue grouped by category: Cloud Credits (Amazon AWS Credits, Google Cloud Startup Program), Insurance and Healthcare (Onsurity TeamSure), Payment Solutions (Razorpay), each Active and Free. Tabs Subscriptions (applied or received), Summary (Applied 0, Confirmed 0 for all four) and Analytics.

On screen: Category, Title, Status, Free/Paid, Applied, Confirmed

Actions available: Add New, Update Tags, Filters, Access, Edit, Delete

Use case. The incubator lists partner offers and startups apply for them.

Example. AgroSense (fictional) applies for AWS credits and the PM confirms the request.

Map applications to startup records/app/tools/mapping

Mappings (application to startup)

26 field mappings, each 'Application -> Startup', from an application pipeline to a startup pipeline (for example KRISHIBOOT 9.0 Applications to KRISHIBOOT 9.0 Startups, NABARD CCF Investment Support 4.0, BIRAC SEED FUND 2023, MEITY SAMRIDH 2.0). They decide which application answers are copied into the startup profile on onboarding.

On screen: From Pipeline, To Pipeline, Type

Actions available: Add New, View, Delete

Use case. An admin sets this up once per call so selected applicants become startups without retyping.

Example. For AgriSpark 3.0 (fictional) the admin maps 'Company PAN' and 'Sector' from the application to the startup profile.

Store documents and issue certificates/app/tools/documents

Documents

Document store root with a single 'Applications' folder (the hub counts 25,819 files). Opening it shows per-pipeline folders (for example KRISHIBOOT 10.0 Applications) with filters, but the file list did not load because its read call was blocked. No certificates folder is visible here.

On screen: Folder: Applications, Pipeline, Filters

Actions available: Open folder, Back

Use case. Staff find the files applicants uploaded, by pipeline.

Example. The PM pulls all pitch decks from the AgriSpark 3.0 (fictional) applications folder.

Store documents and issue certificates/app/tools/certificate

Bulk certificate generator

A hidden tool, not linked from the Tools hub: Step 1 upload a PNG, JPG or PDF background template, with a live preview pane (later steps appear after a template is uploaded).

On screen: Upload Template, Live Preview

Actions available: Choose File (not used)

Use case. Staff issue participation or completion certificates to a whole cohort.

Example. The PM generates 40 'AgriSpark 3.0 (fictional) participation' certificates from one template.

Report and audit usage/app/reports

Reports generator (custom analytics)

A hidden page, not linked from the menu: tabs Reports (none yet), Templates (Executive Summary, Program Performance, Startup Portfolio, Engagement Analytics, Funding and Investment) and Data (available metrics, empty). Reports are built by combining widgets.

On screen: Reports, Templates, Data / Available metrics

Actions available: New Report, Browse Templates, Use template

Use case. Leadership builds dashboards for boards and funders.

Example. The Director starts from 'Funding and Investment' to show the funder how much was disbursed this year.

Report and audit usage/app/setup/sites/usage/resources

Site usage: resources and storage

Site Usage tabs Resources, Download Logs, Inbox, Login History and Video Usage. Resources shows a monthly storage trend (50.31 GB in Jan 2026 to 64.42 GB in Sep 2026), storage by module (application 23,050 docs and 58.57 GB; startup 2,134 and 5.23 GB; announcement 72; grievance 13; survey 2; total 64.45 GB and 25,807 documents), Document Transfer and Emails reports by date range, AI Usage ('No information received') and Organisation Users (24 of 24 seats) with role chips.

On screen: Storage Usage Trend, Storage by Modules, Document Transfer Report, Emails, AI Usage, Organisation Users, Roles: Administrator, Cohort Manager, Course Manager, Evaluation Manager, Fund Manager, Funding Portfolio Manager, Portfolio Manager, Program Manager

Actions available: Year and month pickers, Search, Download, Delete user

Use case. The admin watches plan limits (storage, seats, email) and who holds admin roles.

Example. The admin sees 24 of 24 seats used and removes a departed intern before adding a new Programme Manager.

Report and audit usage/app/setup/sites/usage/downloads

Site usage: download logs

Audit trail of every export: user, email, flow (Application_Submit when an applicant downloads their submitted PDF, Application_List when staff export a list), source pipeline, type (Pdf or Excel) and time.

On screen: User, Email, Flow, Source, Download Type, Downloaded At

Actions available: Search Download Logs, Sort

Use case. The admin checks who exported applicant data, for data-protection audits.

Example. The data protection lead confirms that only two staff exported the AgriSpark 3.0 (fictional) applicant list this month.

Personal workspace/app/task

Tasks

Personal task list with filters All, Assigned To Me and Assigned By Me and a search box. Empty ('No Task(s)').

On screen: All, Assigned To Me, Assigned By Me, Search Tasks

Actions available: Add New

Use case. Staff assign follow-ups to each other.

Example. The PM assigns 'Collect UC from AgroSense (fictional) by 15th' to a programme associate.

Personal workspace/app/user/inbox

Inbox

In-app mail inbox with search; empty for this account ('No Mail'). Chat (/app/chat) is also empty ('No chats found'), with a two-pane layout of conversation list and thread. Message bodies were not opened.

On screen: Search, Message list

Actions available: Search

Use case. Staff and founders exchange messages inside the platform.

Example. A founder messages the PM about a tranche date instead of emailing.

Personal workspace/app/dashboards (bell) and /app/user/notifications

Notifications panel

Slide-over list of notifications; every recent one is a daily digest such as 'n application(s) received in the pipeline - KRISHIBOOT 10.0 Applications on <date>'. The full page /app/user/notifications holds 368, grouped by day (its counter reads 'Showing 1 - 0 of 368').

On screen: Module, Time ago, Message, View All

Actions available: Open full page, View All

Use case. A PM sees new activity without opening each module.

Example. The PM sees '6 applications received' for AgriSpark 3.0 (fictional) and starts screening.

Personal workspaceTop bar 'Find something...' / Cmd+K

Global search (Cmd+K)

A command-palette dialog with a single Search box over a dimmed page; nothing is suggested until you type (not tried).

On screen: Search

Actions available: Type to search (not used)

Use case. Staff jump straight to a startup, application or page.

Example. The PM presses Cmd+K and types 'AgroSense' to open the startup profile.

Personal workspaceTop-right avatar

User menu

Account menu with the user's name and email, then Account, Availability, Calendar, Meetings, Integrations and Sign Out (not clicked). The top bar also has Language and Region (regions India, Americas, Asia Pacific, Europe, Middle East; only English (US)), a Grievance shortcut, Tasks, Inbox, Chat and the notification bell. The dashboard's 'Actions Required' card shows 25 open grievances for this user.

On screen: Account, Availability, Calendar, Meetings, Integrations, Sign Out

Actions available: Open each personal page

Use case. Each user manages their profile, mentoring availability, calendar and integrations.

Example. A mentor sets weekly availability so the PM can book sessions.

Facts observed

Tools hub counts: 569 announcements, 1 notice, 2 surveys, 53 open grievances, 25,819 document files, 4 resources, 26 mappings, 0 accounts, 0 invoices this quarter
All announcements seen are Type 'Email'; no SMS or WhatsApp announcements exist; /app/tools/whatsapp loads a blank page
Announcement recipient counts range from 1 to 133; delivery report example: 46/46 delivered, 46/46 opened, 0/46 clicked; many timestamps read 'Data Not Captured'
Mail templates: 298 in the list (Setup hub says 256); vendor defaults are locked and must be duplicated to change; merge tags such as {{User Name}}, {{Sid}}, {{Updates Title}}
Grievances: 74 in total, 53 open and 21 closed; 73 are 'General' (not tied to a pipeline); new form offers 2 types (Program Related, Platform Related Tech Support), older tickets use 'Technical Issue' and 'Management Issue'
Program Related tickets are assigned to about 20 staff at once; tech-support tickets go to the vendor's support account
No grievance escalation levels configured; one cohort-wise rule (ABI - Call for Incubation 2023) with one assignee and no mail templates
Dashboard 'Actions Required' shows 25 open grievances for the signed-in user, while the hub shows 53 open in total
Example closed ticket (asking for a rejection reason) was closed about 10 months after it was raised, with no reply recorded in the ticket
Surveys: 2, created 2021 and 2022, both 0 responses, both 'last modified' on the same day in Nov 2024 (likely a migration)
Survey options: active toggle, form template, multiple responses, respondent and manager emails, payment after submission, evaluation; public link with QR and embed code, GTM and Facebook Pixel fields
Funding: Grant, Equity and Debt fund lists are all empty; Demo Days is 'Coming Soon'; 1 nomination (Onboarded, by the vendor's support account, Apr 2024) and 1 recipient (₹2,50,000 disbursed, no allocation or fund, a link containing 'undefined')
The funding recipient view tracks allocated, disbursed and expenditure amounts, milestones (active and completed) and tranches (initiate or delete)
Invoices, Accounting (Accounts, Counter Parties) and Setup > Payments: all empty
Resources: 4 free perks (AWS credits, Google Cloud Startup Program, Onsurity TeamSure, Razorpay); 0 applied, 0 confirmed
Mappings: 26, all 'Application -> Startup', one per call (KrishiBoot, AGRI UDAAN, NABARD CCF, BIRAC SEED FUND, MEITY SAMRIDH, ABI)
Storage: 50.31 GB (Jan 2026) to 64.42 GB (Sep 2026); 64.45 GB and 25,807 documents in Oct 2026, of which applications are 58.57 GB and 23,050 documents
Organisation users: 24 of 24 admin and management seats used; roles Administrator, Cohort Manager, Course Manager, Evaluation Manager, Fund Manager, Funding Portfolio Manager, Portfolio Manager, Program Manager
AI usage panel: 'No information received'
Notifications: 368, nearly all 'n application(s) received in the pipeline' digests
Tasks, Inbox and Chat are empty for this admin account
Hidden pages not linked from the menus: /app/reports (Reports Generator, 5 templates, no reports) and /app/tools/certificate (Bulk Certificate Generator)
Language and Region offers regions but only English (US)

Strengths

Announcements are tracked per recipient (delivered, opened, clicked, bounced) with a downloadable report and one-click resend
Templates use merge tags; system emails exist for every event (mentoring, payments, grievances, invoices, onboarding, update reminders)
Surveys are flexible: public link, QR, embed code, payments, evaluation and 'Onboard As' to turn respondents into startups
The grievance desk is reachable from every page (Support link) and is simple for founders: four fields
The funding data model is sound: fund types (grant, equity, debt), stage-based nominations, tranches, milestones and expenditure
Good admin auditing: download logs per user, login history, storage per module, seat usage
Application-to-startup field mapping avoids retyping on onboarding
The Tools hub groups tools by job and shows live counts with pinning

Gaps and friction

Grievances have no reply thread, no SLA or ageing, and no escalation configured; tickets go to about 20 people at once, so nobody owns them; 53 of 74 are open and some were closed months later with no recorded answer
Most grievances are applicants asking for results or reporting upload or edit problems near deadlines, which points to missing status visibility and form-recovery features rather than a support problem
The funding module is unused at a-IDEA: no funds, one orphan recipient, an 'undefined' link, and a tranche date showing the current time; disbursements are clearly tracked elsewhere (spreadsheets)
Invoices, accounting, payments, tasks, chat, resources uptake and the reports generator are all empty: features exist but have not been adopted
Announcements are email only; no SMS or WhatsApp channel (the WhatsApp route is blank)
Announcement view shows the full recipient list (names and emails) inline; staff contact numbers are hard-coded in bodies
Locked system templates must be duplicated to edit, which creates near-duplicate templates (298 vs 256 counts disagree)
Survey forms ask logged-in founders to retype name, email, sector, founders and website instead of pre-filling from the startup profile
Notifications are only 'applications received' digests; there are no actionable alerts (deadlines, overdue reports, pending approvals)
Counts disagree across screens (25 vs 53 open grievances, 25,819 vs 25,807 documents, 'Showing 1 - 0 of 368')
Useful tools are hidden: Reports Generator and Certificate Generator are not linked from the menus
Several detail pages load forever when one call fails, with no error state

For INQB Zone

Grievance desk: one owner per ticket (auto-assigned by programme), a reply thread visible to the founder, SLA timers with escalation levels (PM, COO, Director as in MoU 19.2), and closure only with a resolution note
Reduce grievances at the source: show applicants a live application status and expected result date, and let the PM reopen a submitted form section without a ticket
Announcements: keep per-recipient delivery and open tracking and one-click resend to non-openers, but hide recipient lists by default, use BCC semantics and put staff contact details in centre settings, not in bodies
Add push and email by default and SMS or WhatsApp as paid add-ons (as decided), with one composer and channel choice
Make funding first-class and simple, matching the grants plugin: scheme > sanction > tranches with conditions (late reports hold tranches), PM, head and finance release approvals, expense log drafting the UC; this is what a-IDEA tracks outside Accubate today
Validate and show empty states and errors clearly; never show broken records (orphan recipient, undefined links, a date standing in for missing values)
Surveys should pre-fill from the founder-owned venture profile and write answers back to it (one profile, reused everywhere)
Allow editable copies of system templates with versioning instead of locked defaults plus duplicates
Notifications should be actionable (overdue monthly reports, tranche approvals pending, tickets breaching SLA), not only 'applications received' counts
Copy the download log and seat or storage usage pages for DPDP audits; add who viewed sensitive fields
Put reports and certificates in the main navigation; offer a fixed catalogue of report templates (executive summary, programme performance, funding) as the custom report builder plans
Perks (resources) need a reason to use them: show them in the founder's onboarding checklist and track applied and confirmed

Founder view: profile, calls and applications

The founder side of Accubate at a-IDEA is a thin portal around two kinds of record: applications (one per call) and startup records (one per startup pipeline the founder was onboarded into). Home shows both as cards with clear status (Application: On-Boarded; Form: Submitted or Not Filled; startup Active and '% profile complete'), and a login pop-up lists the exact profile fields and the portfolio (KPI) form still to fill, which is the founder end of the manager's company-profile settings and Not Filled / Saved / Submitted portfolio badge. The startup record itself has a Company Profile (master data, addresses, team members with equity and KYC slots including Aadhaar), Documentation (General, Legal, Financials per year, Yearly Reports, Funding History, Bank Details), Comments, Engagements counters, a Help ticket desk and Milestones, with extra tabs (Application, Portfolio, Documents) when the pipeline enables them; nothing from the submitted application was carried into the 2026 profile. There is no in-app list of open calls: a founder reaches a call only through its public link, which prefills name and email but asks every other question again, and can check status by email OTP. The account area adds roles, a mentor-style personal profile, an Engagements ledger, meeting-app integrations and a self-service data-erasure request; only the application's Pipeline Journey (answers per round) could not be shown, because it loads through a PUT that stays blocked.

Discover a call and apply
Track the application
Sign in and see everything at a glance
Complete the profile after onboarding
Report progress (portfolio / KPI form)
Day-to-day follow-up
Manage the personal account
Leave the platform

Use cases

Founder

AgroSense's founder checks the status of the KRISHIBOOT 10.0 application

Signs in; Home shows the 'KRISHIBOOT 10.0' card under My applications with the current round and two statuses (Application, Form)
If the PM promoted the application, the card shows Round 2 and Form: Not Filled until she fills the private Round 2 form
Clicks View to open the application; Pipeline Journey shows her answers round by round (round names hidden if the PM turned on 'Hide Round')
Without signing in she can instead open the call's public link, click Check under 'Already Applied?', enter her email and the OTP

Example. Fictional: on 30 Oct AgroSense's card changes from Round 1 to Round 2 after the PM promotes the shortlist in the applications list; the manager's Journey column shows a tick for Round 1 and a grey dot on Round 2 for the same application.

Founder

AgroSense's founder updates the company profile after onboarding

The PM onboards the application; a new startup record appears under My Startups at about 30% complete
At next login the 'remaining tasks' pop-up lists the missing company-profile fields the PM marked required in the startup pipeline
She clicks Edit Company Profile (Company Profile tab) and fills TRL, legal status, women-led, revenue and funding stage, adds her co-founder under Team Member(s) and uploads DPIIT and PAN under Documentation > Legal
The percentage rises; the PM's company-profile analytics charts for the cohort now include AgroSense

Example. Fictional: AgroSense goes from 30% to 85% complete; the only fields left are Facebook and YouTube, which still count as missing.

Founder, then Programme Manager

AgroSense submits its quarterly portfolio (KPI) form

The tasks pop-up step 'Portfolio: Portfolio not filled' shows Complete Portfolio Form
The button opens the portfolio form for this startup and pipeline (/ext/startup/portfolio/<startupId>/<pipelineId>)
The founder fills and submits it
In the manager's pipeline workspace the Portfolio column for AgroSense changes from Not Filled to Saved or Submitted

Example. Fictional: AgroSense reports Rs 6 lakh revenue and 5 employees for Q3; the PM sees 'Submitted' but must open the form to see the numbers.

Founder

Founder reviews every programme she has been part of

User menu > Account > Engagements
Reads My Application(s) (ID, pipeline, status, date) and My Startup(s) (ID, pipeline, status, date)

Example. Fictional: AgroSense's founder sees she applied to KRISHIBOOT 9.0 and 10.0 and was onboarded once, into 'KRISHIBOOT 10.0 Startups'.

Applicant / Founder

Applicant asks to be erased

Account > Privacy
Add data eraser request
Personal information is anonymised after 7 days; login and history are lost

Example. Fictional: a rejected applicant to KRISHIBOOT 10.0 files an erasure request in November.

Screens 24

Discover a call and apply/ext/form/24431/1/apply

A call's public page (KRISHIBOOT 10.0)

The only way a founder reaches a call: its public Round 1 link. Green page with the call title, poster, 'Last Date to apply: 28 Oct 2026 11:59:59 pm', a short description, an 'Already Applied? Check your status' box and then the 24 numbered questions. Because a founder is signed in, Name and Email come prefilled (blurred); the founder still answers every other question (date of birth, designation, certificates, photo, entity type, focus area, stage, problem, solution, revenue model, IP, other incubators, Rs 200 registration-fee receipt and UTR). Ends with a terms checkbox, Submit and Save as Draft (not touched).

On screen: Call title, Poster, Last date to apply, Description, Already Applied? Check your status, 24 numbered questions with character counters, Upload your file fields, Fee receipt upload with a-IDEA bank details printed in the question, UTR ID and transaction details, Terms and Privacy consent

Actions available: Check (status), Submit, Save as Draft

Use case. A founder who saw the call on a-IDEA's website or social media opens the link, applies, and later returns to the same page to check status.

Example. AgroSense's founder (fictional, precision-irrigation sensors) opens the KRISHIBOOT 10.0 link from a WhatsApp forward; name and email are already filled because she is signed in, but she must retype her stage, problem and revenue model even though AgroSense already has an Accubate profile.

Track the application/ext/form/24431/1/apply (Check)

Check application status (email OTP)

The 'Check' button opens a 'Check Application Status' modal with one Email field and Send OTP / Cancel. The email is not prefilled even for a signed-in founder. Nothing was typed or sent.

On screen: Email

Actions available: Send OTP, Cancel

Use case. An applicant without a password (or who forgot which account they used) checks where the application stands, straight from the call page.

Example. AgroSense's founder enters her email, receives an OTP and sees that the KRISHIBOOT 10.0 application is in Round 2 (fictional).

Founder home (dashboard)

Welcome line, an a-IDEA noticeboard banner (video/poster), then two card rows. 'My Startups (2)': one card per startup record (named after the startup pipeline, e.g. 'a-IDEA Incubation Startup Details 2026', 'KRISHIBOOT 2.0'), Active badge, startup ID and name (blurred), a '30.0% profile complete' button and View Profile. 'My applications (2)': one card per application with the call name, applied date and time, current round (Round 1, Round 3) and two separate statuses, Application (On-Boarded) and Form (Submitted / Not Filled), with View. Right rail: Quick References (View Library), Actions Required ('You are good for now.'), Upcoming (No upcoming meetings scheduled; Calendar link). The red 'check your network connection' toast in some shots comes from a read the capture tool blocked, not from the product.

On screen: My Startups cards: pipeline name, status, startup ID, % profile complete, My applications cards: call, applied at, round, Application status, Form status, Quick References, Actions Required, Upcoming meetings

Actions available: View Profile, % profile complete (opens tasks), View (application), View Library, Calendar

Use case. The founder's landing page after every login: shows which programmes the startup is in, where each application stands and what is left to do.

Example. After onboarding into KRISHIBOOT 10.0, AgroSense's founder sees a new 'KRISHIBOOT 10.0 Startups' card at 30% complete next to her application card showing Application: On-Boarded, Form: Submitted (fictional).

Left menu and user menu (founder modules)

The founder's whole navigation. Left menu: Home, Mentoring, Resources, Learning, Calendar, Inbox (and Collapse). Top bar: search (Find something, Cmd-K, empty until typed), Language, Grievance, Tasks, Chat (4 unread), notifications bell (not opened) and the user menu: name and email (blurred), Account, Calendar, Meetings, Integrations, Sign Out (Language, Grievance, Tasks and Chat also repeat here on small screens). There is no 'My Startup', 'Applications' or 'Programmes' entry; the startup profile and applications are reached only from the home cards.

On screen: Home, Mentoring, Resources, Learning, Calendar, Inbox, Grievance, Tasks, Chat, Account, Meetings, Integrations

Actions available: Sign Out (not clicked)

Use case. Shows which modules a-IDEA has switched on for founders.

Example. A founder looking for 'my company profile' has to go back to Home and click View Profile, because the menu has no such entry.

Track the application/app/applications/list/<applicationId>/view

One application (founder view)

Header with the application ID (AIDE-xxxxxx), startup name, applicant name and email (blurred), 'Applied on' date and the pipeline name; actions Export to Excel, Print to PDF and Withdraw; Back. Tabs: Pipeline Journey, Documents, Comments (the manager's version also has Announcements and Evaluations). The tab bodies stay on a spinner even with the form-definition read allowed (POST /forms now returns the 5.9 KB form): the answers per round come from PUT /applicationEntities/<id> with body {"RoundIds":["1","2","3"]}, which the page sends on opening and which stays blocked because it is a PUT.

On screen: Application ID, Applicant name and email, Applied on, Pipeline, Pipeline Journey tab, Documents tab, Comments tab

Actions available: Export to Excel, Print to PDF, Withdraw, Back

Use case. The founder reviews what was submitted in each round, downloads a copy or withdraws the application.

Example. AgroSense's founder opens her KRISHIBOOT 10.0 application to re-read the Round 1 answers before the Round 3 pitch and prints them to PDF (fictional).

Track the application/app/user/profile (Engagements tab)

Account > Engagements: all applications and startup records

A ledger of everything this login is linked to. 'My Application(s)': ID, Pipeline, Status, Created At (here a 2022 KRISHIBOOT application and a Sep 2026 'a-IDEA Incubation Startup Details' application, both Onboarded). 'My Startup(s)': startup ID (blurred), pipeline ('June 2022 Incubatees', 'a-IDEA Incubation Startup Details 2026 Startups'), Status Active, Created At. It shows that each onboarding created a separate startup record with its own ID.

On screen: Application Id, Pipeline, Status, Created At, Startup Id, Startup pipeline

Actions available: Application ID links

Use case. The founder (or support) sees the full history of applications and programme enrolments for one login.

Example. AgroSense's founder sees KRISHIBOOT 9.0 (Rejected), KRISHIBOOT 10.0 (Onboarded) and the resulting 'KRISHIBOOT 10.0 Startups' record in one place (fictional).

Complete the profile after onboarding/app/dashboards (modal on login / '% profile complete')

Remaining tasks: complete the company profile

Pops up on the dashboard at login (and from the '% profile complete' button): startup ID and name (blurred), '1 remaining tasks', a numbered stepper and the task 'Company Profile' listing the exact missing fields: Company's Description, Date of Registration, Is Women Led, Legal Status of the Firm, Stage of Startup, Technology Readiness Level (TRL), Has Revenue Been Generated?, Revenue Amount, Funding Stage, Website, Facebook, Instagram, Twitter, LinkedIn, Youtube. One button: Edit Company Profile (goes to the startup profile).

On screen: Startup ID and name, Remaining task count, Stepper, Missing field list

Actions available: Edit Company Profile, Close (X)

Use case. Nudges a newly onboarded founder to fill the company-profile fields the PM marked as required in the startup pipeline.

Example. On her first login after onboarding, AgroSense's founder is told that TRL, legal status and funding stage are missing; she clicks Edit Company Profile and fills them (fictional).

Complete the profile after onboarding/app/dashboards ('30.0% profile complete' on the second card)

Remaining tasks for a second startup record (step 1 of 2)

The same modal for the older 2022 startup record: '2 remaining tasks' with a two-step stepper. Step 1 Company Profile lists a different set of missing fields (Revenue Model, Operation Type, Market Type, TRL, Has Revenue Been Generated?, Revenue Amount, Funding Stage, Twitter, Youtube), because each startup pipeline defines its own profile fields.

On screen: 2 remaining tasks, Step 1 Company Profile, Missing fields

Actions available: Edit Company Profile

Use case. A founder with records in two pipelines must complete two different profiles.

Example. AgroSense, incubated in 2022 and re-registered in 2026, shows two cards, each at 30%, each asking for overlapping data (fictional).

Report progress (portfolio / KPI form)/app/dashboards (tasks modal, step 2)

Remaining tasks: portfolio (KPI) form not filled (step 2 of 2)

Step 2 of the same modal: 'Portfolio - Portfolio not filled' and a 'Complete Portfolio Form' button that links to /ext/startup/portfolio/<startupId>/<pipelineId>. This is the founder side of the manager's Portfolio column (Not Filled / Saved / Submitted). The form itself was not opened, to avoid starting it.

On screen: Portfolio, Portfolio not filled

Actions available: Complete Portfolio Form (not clicked)

Use case. The founder submits the periodic KPI/portfolio form that the PM attached to the startup pipeline.

Example. At quarter end AgroSense's founder clicks Complete Portfolio Form, enters revenue, team size and grants received, and the PM's list flips from Not Filled to Submitted (fictional).

Complete the profile after onboarding/app/startups/list/<startupId>/<pipelineId>/view

Startup profile: Company Profile tab (with team)

The startup record of the 2026 startup pipeline. Header: logo (Change), startup ID and name (blurred), pipeline name, Back, a 30.0% progress bar and an expandable '(1) remaining tasks' line listing the missing fields. Tabs: Company Profile, Documentation, Comments, Engagements, Help, Milestones. Company Profile (Edit, History) shows Onboarding Date (09 Sep 2026 04:38 PM), Expected Graduation Date, Company's Description, Domain and Sectors, Stage of Startup, Legal Status of the Firm, Revenue Model, Operation Type, Market Type, Date of Registration, Is Women Led, TRL, Has Revenue Been Generated?, Revenue Amount, Funding Stage, Website, Connect (Facebook, X, Instagram, LinkedIn, YouTube) and Keywords, all 'Not updated yet' although the application form was submitted. Below: Address(es) (Add Address) and Team Member(s) (Add a Member) with one card: photo, name and email (blurred), Founder, 'Platform Access: Account Owner', View and Edit. History opens 'Company Profile History: No Progression Found in Stage or Legal Status'.

On screen: Onboarding Date, Expected Graduation Date, Company's Description, Domain and Sectors, Stage, Legal Status, Revenue Model, Operation Type, Market Type, Date of Registration, Is Women Led, TRL, Revenue generated / amount, Funding Stage, Website, Social links, Keywords, Addresses, Team members with designation and platform access

Actions available: Change (logo), Edit, History, Add Address, Add a Member, View / Edit member, Back

Use case. The founder keeps the company's master data current after onboarding; the PM's cohort analytics and filters read these fields.

Example. AgroSense's founder sets Stage to 'MVP / Validation' and Legal Status to 'Private Limited'; History would then record the stage progression (fictional).

Complete the profile after onboarding/app/startups/list/<startupId>/<pipelineId>/view (Team Member > View)

Team Member Details (read view)

A modal for one team member: photo, name and email (blurred); Startup Role & Information (Designation: Founder, Equity: 0%); Personal Information (Gender (blurred), Phone Number(s), Date of Birth, Qualification / Highest Degree); Professional Experience (Profession, Experience in years, Companies worked with); and, below the fold, Documents: Aadhar, Permanent Account Number (PAN), Employee ID (all empty here).

On screen: Designation, Equity, Gender, Phone, Date of Birth, Qualification, Profession, Experience (years), Companies worked with, Aadhar, PAN, Employee ID

Actions available: Close

Use case. PM and founder record who is in the team, their equity and their KYC documents.

Example. AgroSense adds its co-founder (CTO, 30% equity) with qualification and PAN; Accubate also offers an Aadhaar slot (fictional).

Complete the profile after onboarding/app/startups/list/<startupId>/<pipelineId>/view (Documentation > General)

Documentation > General

Documentation has six sub-tabs: General, Legal, Financials, Yearly Reports, Funding History, Bank Details. General is a fixed checklist with Document Type, Uploaded At and Upload: One Pager, Incubation Agreement, Investor Pitch Deck, Investor Pitch Video, Corporate Pitch Deck, Corporate Pitch Video, all 'Not Uploaded'.

On screen: Document Type, Uploaded At

Actions available: Upload

Use case. The founder uploads the pitch material and the signed incubation agreement so the PM has them on file.

Example. After signing the stamp-paper agreement, AgroSense's founder uploads the scanned Incubation Agreement here (fictional).

Complete the profile after onboarding/app/startups/list/<startupId>/<pipelineId>/view (Documentation > Legal)

Documentation > Legal (registration and tax documents)

A country selector (India) and a checklist with Document Type, Document Number (if any), Issue date, Uploaded At and Upload: Incorporation Certificate, PAN, GST, DPIIT Certificate, CIN, TIN, Memorandum of Association, Articles of Association, TAN, MSME Certificate, Letter of Signing Authority. All empty here.

On screen: Country, Document Type, Document Number, Issue date, Uploaded At

Actions available: Upload

Use case. Company KYC: the PM checks DPIIT, CIN, PAN and GST before agreements, grants or scheme applications.

Example. AgroSense uploads its DPIIT certificate with number and issue date so the PM can include it in a SISFS application (fictional).

Report progress (portfolio / KPI form)/app/startups/list/<startupId>/<pipelineId>/view (Documentation > Financials)

Documentation > Financials (per financial year)

One row per financial year from FY 2022-2023 to FY 2026-2027 with Expenditure, Revenue, Net Balance, Status (Not Filled) and Update, plus Add More. Yearly Reports (not shown) is a similar grid with Balance Sheet, Audit Report and Annual Report uploads per year; Funding History and Bank Details both read 'No ... found' with Add New.

On screen: Financial Year, Expenditure, Revenue, Net Balance, Status

Actions available: Update, Add More

Use case. Yearly financial summary the PM uses for reports to funders; a second KPI channel next to the portfolio form.

Example. In April AgroSense updates FY 2025-2026 with Rs 4.2 lakh expenditure and Rs 6 lakh revenue and uploads the audited balance sheet (fictional).

Day-to-day follow-up/app/startups/list/<startupId>/<pipelineId>/view (Comments)

Startup profile: Comments

A message box ('Add your message...') with Post and a 'Visible To' selector defaulting to Public; 'No Comments' yet. Nothing was typed or posted.

On screen: Message, Visible To (Public by default)

Actions available: Post, Visible To

Use case. Founder and incubation team leave notes on the startup record.

Example. The PM notes 'Pitch deck needs a market-size slide' on AgroSense's record; the founder replies below (fictional).

Day-to-day follow-up/app/startups/list/<startupId>/<pipelineId>/view (Engagements > Analytics)

Startup profile: Engagements (analytics)

Two sub-tabs, Analytics and Engagements. Analytics shows four counters: Total Funding Allocated, Total Mentorings, Total Meetings, Total Meeting Duration (all 0). The Engagements sub-tab reads 'Engagements not found'.

On screen: Total Funding Allocated, Total Mentorings, Total Meetings, Total Meeting Duration

Use case. A quick view of how much support the startup has received; feeds the manager's engagement leaderboard.

Example. After two mentor sessions and a Rs 5 lakh grant tranche, AgroSense's counters read 2 mentorings and Rs 5,00,000 allocated (fictional).

Day-to-day follow-up/app/startups/list/<startupId>/<pipelineId>/view (Help)

Startup profile: Help (support tickets)

Counters Total Tickets, Open Ticket(s), Closed Ticket(s) and 'Have Issues? Raise a Ticket'; filters All / Open / Closed and Search; empty state 'No Tickets Raised, Raise your first ticket' with Raise a Ticket.

On screen: Total / Open / Closed tickets

Actions available: Raise a Ticket, Filters, Search

Use case. The startup asks the incubator for help (lab access, documents, payments) and tracks the answer.

Example. AgroSense raises a ticket asking for soil-lab access next week; it shows as Open until the facility team closes it (fictional).

Report progress (portfolio / KPI form)/app/startups/list/<startupId>/<pipelineId>/view (Milestones)

Startup profile: Milestones

'No Milestones Found' with Add a Milestone (also in the header). The founder can add milestones to the startup's own record.

On screen: Milestones list

Actions available: Add a Milestone

Use case. Founder and PM track agreed milestones (prototype, first customer, grant condition) on the record.

Example. AgroSense adds 'Field trial on 20 acres by March 2027' as a milestone tied to its second grant tranche (fictional).

Complete the profile after onboarding/app/startups/list/<startupId>/<pipelineId>/view (June 2022 Incubatees)

Older startup record: more tabs, empty bodies

The 2022 record of the same company in the 'June 2022 Incubatees' pipeline: 30.0%, '(2) remaining tasks' (Company Profile with 9 fields; Portfolio not filled) and nine tabs: Company Profile, Documentation, Application, Portfolio, Documents, Comments, Engagements, Help, Milestones, so the tabs depend on the modules switched on for each startup pipeline. The tab bodies stayed empty because they also need POST /startupEntities/Ids, which stays blocked.

On screen: Remaining tasks, Tabs: Application, Portfolio, Documents (extra)

Actions available: Add a Document (header, on Documents), Back

Use case. Shows that one company can carry several startup records with different tab sets and different missing fields.

Example. AgroSense's 2022 record has a Portfolio tab and an Application tab (copy of the 2022 application), while its 2026 record has neither (fictional).

Day-to-day follow-up/app/task

Tasks

Task list with filter chips All / Assigned To Me / Assigned By Me and Search Tasks; this founder has none ('No Task(s)'). The Filters panel failed with 'Something went wrong' once.

On screen: All, Assigned To Me, Assigned By Me, Search

Actions available: Filters

Use case. Where a PM's assigned to-dos for the startup would appear; separate from the profile 'remaining tasks' checklist and from the home 'Actions Required' box.

Example. The PM assigns AgroSense 'upload the signed incubation agreement by 15 Nov'; it would show here under Assigned To Me (fictional).

Manage the personal account/app/user/profile

Account > Settings

Profile photo (blurred) with Change and Download, the name (blurred) and six tabs: Settings, Personal Profile, Logs, Bookmarks, Engagements, Privacy. Settings shows Role chips (Applicant, Startup owner, User), Tags (none), E-mail (blurred) with a Verify link (not yet verified), Phone Number(s) (none, Add), Password (masked, Change Password) and Email preferences ('You will receive all announcements from the platform', Update). Logs and Bookmarks were empty.

On screen: Role, Tags, E-mail + Verify, Phone numbers, Password, Email preferences

Actions available: Change (photo), Download, Verify, Add (phone), Change Password, Update (email preferences)

Use case. Founder checks which roles the login has and manages contact details and notification preferences.

Example. AgroSense's founder adds her WhatsApp number and verifies her email so programme announcements reach her (fictional).

Manage the personal account/app/user/profile (Personal Profile tab)

Account > Personal Profile

Read view of the person's profile with Edit links: Name*, Gender*, Date of Birth*, Permanent Address, Current Address, Current Designation*, Current Organisation*, Tagline*, About*, Social Media (LinkedIn, Facebook, X, Instagram); Professional Achievements & Journey (Career Highlights*, Industry Experience*, Leadership Roles*); Experience (Add); Files (Add). Almost all fields are empty ('No information added'). The same profile shape serves mentors and founders.

On screen: Name, Gender, Date of Birth, Addresses, Designation, Organisation, Tagline, About, Social media, Career Highlights, Industry Experience, Leadership Roles, Experience, Files

Actions available: Edit, Add

Use case. The person-level profile (not the company) that mentors, PMs and the directory see.

Example. Before a mentoring session, AgroSense's founder fills her tagline and experience so the mentor knows her background (fictional).

Manage the personal account/app/user/integrations

Integrations: meeting apps

'Meeting apps, 0 of 4 connected': Webex (meetings and meeting summaries), Zoom (meetings), Google Meet and Calendar (meetings, calendar sync), Microsoft Teams and Outlook Calendar (meetings, calendar sync), each Disconnected with Manage; Jitsi Meet needs no connection and is the 'Default for meetings', with a warning that the host must register and sign in to Jitsi before a meeting can start.

On screen: Provider, Connected/Disconnected, Capabilities (Meetings, Calendar, Meeting summaries), Default for meetings

Actions available: Manage

Use case. A founder connects a calendar or meeting app so mentoring sessions and events create links and sync to their calendar.

Example. AgroSense's founder connects Zoom so that the PM's booked mentor sessions arrive with Zoom links (fictional).

Leave the platform/app/user/profile (Privacy tab)

Account > Privacy: erase my data

One row, 'Erase my data', with an 'Add data eraser request' link and the warning that the request is irreversible: all personal information is anonymised in 7 days, the person can no longer log in and loses access to applications, startups and mentoring history.

On screen: Erase my data

Actions available: Add data eraser request (not clicked)

Use case. A data principal's self-service erasure request (relevant to the DPDP Act).

Example. An applicant who was rejected and does not want her data kept files an erasure request; after 7 days her records are anonymised (fictional).

Facts observed

Founder left menu: Home, Mentoring, Resources, Learning, Calendar, Inbox; top bar: search, Language, Grievance, Tasks, Chat, notifications, user menu (Account, Calendar, Meetings, Integrations, Sign Out). No menu entry for the startup profile, applications or open calls.
Probed /app/applications, /app/programs, /app/startup/programs, /app/opportunities, /ext/programs, /ext/forms, /ext/opportunities: all 404 or redirect to Home. Founders have no in-tenant directory of open calls; the admin setting 'auto-enable public listing of new application forms on accubate.app' points to the vendor's own listing instead.
This founder login holds 2 applications and 2 startup records: a 2022 KRISHIBOOT application (reached Round 3; Application On-Boarded, Form Not Filled) that became a 'June 2022 Incubatees' startup, and a 9 Sep 2026 application to 'a-IDEA Incubation Startup Details' (Round 1, Form Submitted, On-Boarded) that became an 'a-IDEA Incubation Startup Details 2026 Startups' record 11 minutes later.
a-IDEA ran its 2026 incubatee census as an application pipeline: existing incubatees fill an application form and are onboarded into a 2026 startup pipeline, creating a second startup record (new ID, the company name spelled differently) for the same company.
Application cards carry two independent statuses: Application (decision, e.g. On-Boarded) and Form (Submitted / Not Filled for the current round's form); an application can be onboarded while its Round 3 form is still Not Filled.
Both startup records show 30.0% profile complete. Remaining tasks: 2026 record 1 task (Company Profile, 15 missing fields incl. Website, Facebook, Instagram, Twitter, LinkedIn, Youtube); 2022 record 2 tasks (Company Profile with 9 missing fields; Portfolio not filled).
Home 'Actions Required' says 'You are good for now.' while the same page's pop-up says there are 1 and 2 remaining tasks.
Portfolio form link pattern: /ext/startup/portfolio/<startupId>/<pipelineId>; startup profile: /app/startups/list/<startupId>/<pipelineId>/view; application: /app/applications/list/<applicationId>/view.
Founder's application page has tabs Pipeline Journey, Documents, Comments and actions Export to Excel, Print to PDF, Withdraw; the manager's page also has Announcements and Evaluations.
Opening an application page automatically sends PUT /applicationEntities/<id> with body {"RoundIds":["1"]} (blocked by the tool): the page writes on view.
Public call KRISHIBOOT 10.0: last date 28 Oct 2026 11:59:59 pm, 24 questions, Rs 200 registration fee paid by bank transfer to a-IDEA's account (details printed in the question) with receipt upload and UTR typed by hand; status check by email OTP; 'This form was created inside of aideanaarm.accubate.app, Powered by Cunomial'.
Account roles shown as chips: Applicant, Startup owner, User. Email shows 'Verify' (unverified); no phone; email preference 'receive all announcements'.
Meeting integrations: Webex, Zoom, Google Meet and Calendar, Microsoft Teams and Outlook Calendar (0 of 4 connected); Jitsi Meet is the default fallback with nothing to connect.
Privacy tab: self-service 'Add data eraser request'; personal data anonymised in 7 days; irreversible.
Chat shows 4 unread (not opened); Tasks: none.
2026 startup record tabs: Company Profile, Documentation, Comments, Engagements, Help, Milestones. 2022 record tabs: Company Profile, Documentation, Application, Portfolio, Documents, Comments, Engagements, Help, Milestones. No IPR or Canvas tab is visible on either record, although the page markup contains hidden Lean Canvas / Business Canvas and funding Recipients / Nominations sections (modules switched off in the pipeline).
Company Profile fields: Onboarding Date, Expected Graduation Date, Company's Description, Domain and Sectors, Stage of Startup, Legal Status, Revenue Model, Operation Type, Market Type, Date of Registration, Is Women Led, TRL, Has Revenue Been Generated?, Revenue Amount, Funding Stage, Website, Connect (5 social links), Keywords; plus Addresses and Team Members. All read 'Not updated yet' on the 2026 record although its application form was submitted 11 minutes before onboarding.
Company Profile History tracks only progression in Stage or Legal Status ('No Progression Found in Stage or Legal Status').
Team member record: Designation, Equity %, Platform Access (Account Owner), Gender, Phone, Date of Birth, Qualification, Profession, Experience (years), Companies worked with, and document slots Aadhar, PAN, Employee ID.
Documentation > General: One Pager, Incubation Agreement, Investor Pitch Deck and Video, Corporate Pitch Deck and Video. Legal (country = India): Incorporation Certificate, PAN, GST, DPIIT, CIN, TIN, MOA, AOA, TAN, MSME, Letter of Signing Authority, each with document number and issue date. Financials: FY 2022-23 to 2026-27 rows with Expenditure, Revenue, Net Balance, Status. Yearly Reports: Balance Sheet, Audit Report, Annual Report per FY. Funding History and Bank Details: empty, Add New.
Revenue is asked in four places on the founder side: the application form, Company Profile (Has Revenue Been Generated?, Revenue Amount), Documentation > Financials per FY, and the portfolio form.
Startup Comments default to 'Visible To: Public'.
Startup Engagements analytics: Total Funding Allocated, Total Mentorings, Total Meetings, Total Meeting Duration (all 0 here); Help desk: Total / Open / Closed tickets with Raise a Ticket; Milestones: Add a Milestone (founder can add).
The application page's answers load through PUT /applicationEntities/<id> with body {"RoundIds":[...all rounds...]}; POST /forms only returns the form definition (5.9 KB).

Strengths

One login sees all its applications and startup records across years; the Engagements tab is a clean ledger (ID, pipeline, status, date).
Status is split into decision (Application) and completion (Form), which answers both 'was I selected?' and 'do I owe a form?'.
The remaining-tasks pop-up names the exact missing fields and links straight to the place to fix them; the portfolio step makes KPI reporting a visible to-do.
Applicants can check status from the public call page with an email OTP, without a password.
Founders can export or print their own application and withdraw it themselves.
Self-service erasure request with plain-language consequences.
Meeting-app integrations with a no-setup Jitsi fallback.

Gaps and friction

No directory of open calls inside the app or on the founder home; founders depend on links shared elsewhere.
No reuse of the venture profile: each call asks the same questions again (only name and email prefilled) and each onboarding creates a new startup record, so one company ends up with several IDs, spellings and half-filled profiles (30% each here).
Contradictory signals: 'Actions Required: You are good for now' next to a pop-up with 1-2 remaining tasks; three different to-do concepts (Actions Required, remaining tasks pop-up, Tasks page).
Startup profile and applications are missing from the left menu; they are reachable only from home cards.
Social handles (Facebook, Instagram, Twitter, YouTube) count as missing profile tasks, inflating incompleteness and nagging founders about irrelevant fields.
Fees are handled by printing a bank account in the form and asking for a receipt upload and a typed UTR; no payment link or automatic matching.
The application page writes to the server when merely opened.
The status-check modal asks a signed-in founder for email and OTP again.
The personal profile is mentor-shaped (career highlights, leadership roles, starred as required) and asks for date of birth and addresses; email unverified, no phone.
The founder never sees evaluation feedback: the founder's application page has no Evaluations or Announcements tab.
The company profile is not prefilled from the submitted application: every field is 'Not updated yet' on a record created from a submitted form.
Team-member KYC has an Aadhaar document slot, and DOB, gender and equity sit in the same record that PMs and mentors open.
Revenue and financial data are collected in four unconnected places (application, company profile, Financials per FY, portfolio form), with no single source of truth.
Profile history covers only Stage and Legal Status, not other edits.
Comments default to 'Public' visibility.
Tabs differ by pipeline and the older record has both 'Documentation' and 'Documents' tabs, which is confusing.
The incubation agreement is only an upload slot; nothing is generated or signed in the system.
The application's answers are fetched with a PUT, so a read looks like a write; the founder's Pipeline Journey could not be inspected safely.

For INQB Zone

Give founders a 'Programmes' page and a home widget listing open calls (INQB's public directory of open calls, dated and rolling), with one-click apply from the existing venture profile.
Keep exactly one founder-owned venture profile and reuse it for every application (snapshot per submission, INQB rule), so a company never gets a second record or ID when it joins a new programme.
Copy the two-part status (decision vs. form owed) and the field-level 'complete your profile' checklist, but merge Actions Required, profile tasks and assigned tasks into one consistent to-do list.
Copy the Engagements ledger: one place listing every application, programme membership and status for the login.
Make the portfolio/KPI form a dated to-do with reminders and show the PM the values, not just Not Filled / Saved / Submitted; late reports can hold tranches (INQB rule).
Show the founder's journey round by round with applicant feedback but no scores or evaluator names (INQB rule), which Accubate does not show at all.
Do not count social handles toward completeness; weight the fields that matter to the programme.
Never write on page view; opening a record must be read-only.
Replace bank-detail text and receipt uploads with INQB's fee flow (UTR verification, receipts generated by INQB Zone).
Offer a self-service erasure request that follows the MoU: founder-owned profile erased, the copy inside an a-IDEA application kept as a-IDEA's data, backups cleared within 28 days.
Put 'My startup', 'Applications' and 'Programmes' in the founder's main menu.
Prefill the venture profile from the application snapshot and keep one profile per venture across programmes; never show an onboarded startup an empty profile.
Copy the document checklist by category (General, Legal with number and issue date, Financials per FY, yearly reports), add expiry and missing-document reminders, and generate the incubation agreement from a template (INQB onboarding plugin) instead of a bare upload slot.
Do not offer an Aadhaar slot (INQB rule); keep PAN and bank details encrypted and finance-only, away from the team card mentors see.
Take revenue and financial figures once (monthly health report and quarterly report) and derive the FY view and funder exports from them.
Keep a full field-level audit history on the venture profile, not just stage and legal status.
Default comments on a startup record to the programme team, not Public.
Copy the per-startup help desk counters and the founder-editable milestones, and link milestones to grant tranche conditions.

Founder view: support, reporting and help

After onboarding, a founder (startup user) at a-IDEA sees a six-item menu (Home, Mentoring, Resources, Learning, Calendar, Inbox) plus top-bar shortcuts for Grievance, Tasks and Chat. Each support module the Programme Manager configures per pipeline has a founder-side screen (request a mentor, see sessions, courses and library, claim perks, raise a ticket), but at a-IDEA almost all of them are empty for this founder: no mentors in either of the founder's pipelines, no sessions, courses, library files or events, an empty inbox and calendar. Funding, surveys, announcements and the noticeboard are not available to founders at all ('Permission denied', 'Not authorized' or a blank page), and there is no founder-side progress-report or KPI form because no update schedule is configured in any pipeline. The only lively founder-side channel is a cohort-wide group chat. Route guards are uneven: a founder can open the hidden admin Bulk Certificate Generator, the document store root and the events manager by URL, and the Tools hub shows the site-wide open-grievance count. Outside the tenant, accubate.app runs a public marketplace of programmes, events and offers (187 programmes from 44 organisations, a-IDEA lists only KRISHIBOOT 10.0), which the founder app does not link to.

Find and request a mentor
Mentoring relationships, meetings and feedback
Events and RSVP
Learning: sessions, courses, library
Perks and resources
Funding status (nominations, tranches)
Documents and certificates issued to the startup
Raise a grievance or support ticket
Chat, inbox and calendar
Find the next call (public marketplace)

Use cases

Founder

Request a mentor

Open Mentoring > Connection Request
Select Startup (which startup record), then Select Pipeline
Search the mentors attached to that pipeline
Send a connection request on a mentor card
Wait for approval (auto-rejected after 7 days if not approved, per manager settings)
See the mentor under Relationships and booked slots under Meetings and the Calendar

Example. AgroSense (fictional) asks a fictional post-harvest expert for an anchor mentorship; at a-IDEA today the founder stops at step 3 with 'No mentors available'.

Founder

Attend a learning session

Open Learning > Sessions
Filter Upcoming and the cohort pipeline
Open the session, join (virtual) or scan the QR code (physical)
Give feedback; watch the recording later

Example. A fictional 'Writing a BIRAC BIG proposal' session for the 2026 cohort; today the founder's list is empty because the only session is a test shared with other pipelines.

Founder

Claim a perk

Open Resources
Select View: choose the startup record
Browse More Resources and claim a perk
Track it under Resources already subscribed

Example. AgroSense (fictional) claims cloud credits; the incubator sees Applied 1, Confirmed 0 on its Resources summary.

Founder

Raise and track a support ticket

Click the pencil (Grievance) icon or the footer 'Support' link
Raise a Ticket: title, type (Program Related or Platform Tech Support), details, optional file
Submit (reCAPTCHA)
Track it under Grievances > Open / Closed

Example. AgroSense (fictional) reports that its incubation certificate has not been issued; the ticket reaches about 20 staff and has no programme tag.

Founder or alumni

Find the next programme after graduation

Go to accubate.app > Programs (not linked from the tenant app)
Filter by organisation, sort and search
Apply now on a card, which opens that tenant's public form

Example. A graduating a-IDEA startup (fictional) finds an accelerator call from another incubator closing next month.

Screens 19

Mentoring relationships, meetings and feedback/app/mentoring (= /app/mentoring/mentee/list)

Mentoring (founder): Relationships tab

The founder's Mentoring page with four tabs: Relationships, Meetings, Feedbacks and Connection Request. Relationships reads 'No mentorings'; Meetings reads 'No meetings found' and Feedbacks 'No feedbacks received'. There is no filter, no explanation of what mentoring the programme offers and no call to action in the empty state.

On screen: Tabs: Relationships, Meetings, Feedbacks, Connection Request, Empty state text only

Actions available: None on the empty tabs

Use case. A founder checks who their assigned (anchor) mentor is, upcoming mentor meetings and feedback they have received or owe.

Example. The founder of AgroSense (fictional), a precision-irrigation startup in the 2026 incubation cohort, opens Mentoring a month after onboarding and finds nothing assigned, with no hint whether a mentor will be allocated or must be requested.

Find and request a mentor/app/mentoring/mentee/mentors

Mentoring (founder): Connection Request (find a mentor)

The 'find a mentor' screen. The founder first picks which of their startup records to act for (Select Startup, here two records from two programmes) and then a pipeline (Select Pipeline, one per startup record), then searches the mentors attached to that pipeline. For both of this founder's pipelines (the 2026 incubation pipeline and a 2022 incubatee pipeline) it shows 'No mentors available'. Mentor cards and the request button were therefore never visible.

On screen: Select Startup (startup ID + name), Select Pipeline, Search, Mentor cards (none)

Actions available: Request connection on a mentor card (not present, not clicked)

Use case. A founder looks for a domain mentor in their programme and sends a connection request that the PM or mentor approves (auto-rejected after 7 days if unapproved, per the manager-side settings).

Example. AgroSense (fictional) wants a soil-science mentor; the founder selects the startup and the 2026 incubation pipeline and sees an empty directory, because a-IDEA has attached mentors to only one pipeline (AGRI UDAAN 8.0, one staff mentor).

Events and RSVP/app/events

Events (reachable by URL only)

Events is not in the founder's menu, but the URL opens a page titled 'Events, Manage your event(s)' (admin wording) with Add filter and Search Events. The list area is completely blank: no events and not even an empty-state message. a-IDEA has 0 events on the manager side, so there is nothing to RSVP to.

On screen: Add filter, Search Events

Actions available: None visible

Use case. A founder would browse upcoming demo days, workshops and pitch events and RSVP.

Example. AgroSense (fictional) hears about a field-day workshop by email; the founder looks for it in the app, but Events is not in the menu and the URL shows a blank page.

Learning: sessions, courses, library/app/learning

Learning hub (founder)

The same three-card hub the manager sees: Scheduled delivery (Sessions, '0 upcoming sessions'), Self-paced study (Courses, '0 courses') and Reference material (Library, '0 items'), with a Pinned row ('No items pinned') and a star on each card to pin it. The home dashboard's 'Quick References: View Library' link lands on the Library, which reads 'No files uploaded'.

On screen: Pinned, Sessions count, Courses count, Library count

Actions available: Pin a card (star, not clicked), Open Sessions, Courses, Library

Use case. A founder looks for scheduled masterclasses, self-paced courses and reference documents (templates, scheme guidelines) shared with their cohort.

Example. The founder of AgroSense (fictional) wants a DPR template for a NABARD application; the library is empty.

Learning: sessions, courses, library/app/learning/session

Sessions list with filters (founder)

Sessions list with the Filters panel open: Pipeline (All 0), Conduct Type (All, Virtual, Physical, all 0) and Status (All, Completed, Upcoming, all 0), plus Search Sessions, and an empty state 'No sessions'. The manager side holds one 'Test Session' shared with five other pipelines, so a founder only sees sessions shared with their own pipelines.

On screen: Pipeline, Conduct Type (Virtual/Physical), Status (Completed/Upcoming), Search Sessions

Actions available: Filter radio buttons, Search

Use case. A founder finds the next session for their cohort, joins it (QR attendance on the manager side) and later watches the recording.

Example. A 'GST for agri-startups' session (fictional) would appear here under Upcoming for the 2026 cohort; today the list is empty.

Learning: sessions, courses, library/app/learning/course

Courses (founder)

Self-paced courses list with status chips All, Ongoing, Upcoming, Completed and a search box; 'No courses found'. Library (/app/learning/library) is equally empty ('No files uploaded') and was not captured separately.

On screen: Status chips: All, Ongoing, Upcoming, Completed, Search Courses

Actions available: Filter chips, Search

Use case. A founder enrols in and works through modules, lectures and assignments at their own pace.

Example. A fictional 'Agri value-chain basics' course with five modules would show here as Ongoing; none exist at a-IDEA.

Perks and resources/app/startup/resources

Resources (perks) for the startup

The founder's perk page: a 'Select View' dropdown to choose which startup record to act for, and two tabs, 'More Resources' (perks the startup can claim) and 'Resources already subscribed'. Both stayed empty in this read-only run because the list calls are POST requests that the capture tool blocks; the manager side lists 4 free perks (two cloud-credit programmes, a health-insurance plan and a payments product), 0 applied.

On screen: Select View (startup record), Tabs: More Resources, Resources already subscribed

Actions available: Claim or apply for a perk (cards not loaded, not clicked)

Use case. A founder claims partner perks such as cloud credits once incubated; the incubator sees applied and confirmed counts.

Example. AgroSense (fictional) would claim cloud credits for its sensor-data backend from 'More Resources' and then see it under 'Resources already subscribed'.

Funding status (nominations, tranches)/app/funding/grant (also /app/funding, /nominations, /recipients)

Funding: permission denied for founders

Every funding URL gives a blank page with a red 'Permission denied' toast. There is no founder-side view of nominations, sanctioned amounts, tranches or utilisation, and nothing about funding appears on the founder's home. (The manager-side funding module is itself empty at a-IDEA.)

On screen: Toast: Permission denied

Actions available: None

Use case. A founder would want to see whether they were nominated for seed funding, the next tranche condition and what utilisation report is due.

Example. AgroSense (fictional) receives ₹5 L of a ₹10 L grant; to learn when the second tranche is released, the founder has to email the PM because nothing is visible in the app.

Documents and certificates issued to the startup/app/tools/documents

Document store (founder)

Reachable by URL (not in the menu). Shows the same single 'Applications' folder the administrator sees; opening it shows 'Documents(Applications)' with a Back link and no files. There is no 'issued to you' area for offer letters, agreements or certificates.

On screen: Folder: Applications, Back

Actions available: Open folder

Use case. A founder would download the incubation agreement, offer letter or completion certificate the incubator issued.

Example. AgroSense (fictional) needs its incubation certificate for a DPIIT application; there is no place in the app where it can be found.

Documents and certificates issued to the startup/app/tools/certificate

Bulk Certificate Generator opens for a founder

The hidden admin tool loads for a founder account: 'Bulk Certificate Generator, Create and personalize certificates in bulk', Step 1 Upload Template (PNG, JPG or PDF background) and a Live Preview pane. It is a route-guard gap rather than a founder feature: founders have no list of certificates issued to them.

On screen: Step 1 Upload Template, Live Preview

Actions available: Choose File (not used)

Use case. Meant for staff issuing participation or completion certificates in bulk; shown here only to document that founders can reach it.

Example. A PM would upload a certificate background and merge 30 cohort names; a founder can open the same page by URL.

Raise a grievance or support ticket/app/tools

Tools hub as a founder sees it

The Tools hub trimmed to one card, 'Requests and resolution', with Grievances described in admin terms ('Complaints, escalation levels and their settings') and the site-wide count '53 open grievances', although this founder has raised none. Surveys are mentioned in the section text but have no card.

On screen: Pinned, Grievances card with open count

Actions available: Pin (star), Open Grievances

Use case. Entry point to support for a founder who navigates by URL; not linked from the founder menu.

Example. A founder sees '53 open grievances' and may assume the incubator is slow to respond, an internal metric leaking to users.

Raise a grievance or support ticket/app/tools/grievance (top-bar pencil icon)

My grievances (founder)

The founder's own ticket list: Raise a Ticket (top right and in the empty state), Analytics link, filter chips All, Open, Closed and Search. Empty: 'No Tickets Raised, Raise your first ticket.'

On screen: Filter chips: All, Open, Closed, Search, Analytics

Actions available: Raise a Ticket (seen, not clicked), Analytics

Use case. A founder tracks the status of tickets they raised with the incubator or the vendor's tech support.

Example. AgroSense (fictional) raised a ticket about a failed document upload; the founder filters Open to see whether anyone replied.

Raise a grievance or support ticket/ext/grievance/register (footer 'Support' link)

Report an Issue form (view only)

A public-style form on a green background: Summary/Title (250 characters), Type of Issue (Program Related or Platform Related Tech Support), detailed explanation (5,000 characters) and an optional Supporting Document, then Submit (reCAPTCHA protected). For a signed-in founder nothing asks which programme or startup the issue concerns, which is why almost all tickets land as 'General'. A '250 character(s) remaining' counter is wrongly shown under the radio buttons.

On screen: Summary/Title, Type of Issue, Explain your problem in detail, Supporting Document

Actions available: Upload your file (not used), Submit (not clicked)

Use case. A founder reports a programme problem (delayed result, wrong status) or a platform bug.

Example. The founder of AgroSense (fictional) reports that the second tranche request is pending for six weeks, choosing 'Program Related'; the ticket goes to about 20 staff at once and carries no programme tag.

Chat, inbox and calendar/app/chat (top-bar chat icon, badge 4)

Chat (founder): cohort group chat

Two-pane chat: a conversation list with search and, on the right, the open thread with a '107 Members' dropdown, a thread search and a 'Type a message' composer. The founder's only conversation is the KRISHIBOOT 2.0 cohort group (107 members, 4 unread). Opening the page auto-opens the group thread (message bodies are blurred here) and fires a read-receipt call, which the capture tool blocked. The thread holds a handful of greetings from 2022 to 2026, including one member posting a personal mobile number to all 107 members.

On screen: Conversation list (name, last time, unread count), Members dropdown, Thread search, Composer

Actions available: Type a message / send (not used), Members list (not opened)

Use case. Cohort founders talk to each other and to the programme team in one group per cohort.

Example. Founders of a fictional KRISHIBOOT cohort use the group to ask whether pitch slots are out; with no moderation or pinned notices, questions sit unanswered.

Chat, inbox and calendar/app/user/inbox

Inbox (founder)

In-app mail list with search; 'No Mail'. The 569 email announcements a-IDEA has sent (mostly round results) do not appear here, so the founder has no in-app record of what the incubator told them.

On screen: Search, Message list (empty)

Actions available: Search

Use case. A founder would look back at notices and results sent by the incubator.

Example. AgroSense (fictional) wants the shortlisting email again to check the pitch date; it is only in the founder's personal mailbox.

Chat, inbox and calendar/app/user/calendar

Calendar (founder), month view

Personal calendar headed with the founder's name and photo (blurred), October 2026 month grid with Previous, Today, Next and a view switch (Month shown; the manager side also offers Day, Week and Agenda). No entries: it would show mentor meetings and learning sessions the founder is part of. The user menu also has 'Meetings' (/app/user/meetings), which reads 'No meetings found'.

On screen: Month grid, Today, View switch

Actions available: Navigate months, Change view

Use case. A founder checks the week's mentor meetings, sessions and pitch slots in one place.

Example. A booked mentor slot with a fictional dairy-supply-chain expert would appear on Thursday the 15th; nothing is scheduled.

Find the next call (public marketplace)https://www.accubate.app/en/programs

Accubate public marketplace: All programs

Vendor-run public listing of open calls across all Accubate tenants: an Organizations filter (44 incubators and corporates), sort, search, grid or list view and programme cards with organisation, closing date and 'Apply now'. It shows 187 programmes on one page, 48 with a closing date and 139 without. a-IDEA appears once (KRISHIBOOT 10.0, 'Closes 29 Oct 2026', while the call's own form says last date 28 Oct). The tenant app does not link here; there is a 'Subscribe to get notified' button.

On screen: Organizations filter, Sort by, Search programs, Card: programme, organisation, Closes date, Apply now

Actions available: Apply now (not clicked), Subscribe to get notified (not clicked)

Use case. A founder (or a first-time applicant) discovers open calls from many incubators in one place.

Example. AgroSense (fictional), graduating from a-IDEA, filters by organisation to find an accelerator call that closes next month.

Events and RSVPhttps://www.accubate.app/en/events

Accubate public marketplace: All events

Public event listing with Ongoing Events and Past Events tabs, filters by Incubator, Category (Awards, Competition, Conference, Meetup...) and Sub Category, and event cards (Upcoming, Physical, organiser, category, closing time, View Details). 7 events from 3 incubators; none from a-IDEA.

On screen: Ongoing / Past tabs, Incubators filter, Category, Sub Category, Event card

Actions available: View Details (not clicked)

Use case. Founders discover public competitions and conferences run by any Accubate customer.

Example. A founder finds a fictional cleantech pitch competition and registers through its public page.

Perks and resourceshttps://www.accubate.app/en/offers

Accubate public marketplace: All offers

Public perk marketplace: filters by category (CRM, Marketing, Operations, Design) and organisation, and 6 offers from 2 vendors (5 CRM and marketing products from one CRM vendor, 1 design package from a studio) with a value or discount and 'Get offer' / 'More info'. None of them match the 4 perks a-IDEA configured for its own startups.

On screen: Filter by Category, Filter by Organization, Offer: title, vendor, value/discount

Actions available: Get offer (not clicked), More info

Use case. Startups on any Accubate tenant browse vendor deals.

Example. AgroSense (fictional) takes a 20% discount on a marketing-automation tool.

Facts observed

Founder menu: Home, Mentoring, Resources, Learning, Calendar, Inbox; top bar: search, Language, Grievance (pencil), Tasks (briefcase), Chat (badge 4), notification bell, avatar menu (Account, Calendar, Meetings, Integrations, Sign Out).
Not in the founder menu: Events, Funding, Updates or reports, Surveys, Documents, Certificates, Noticeboard.
This founder holds 2 startup records (one per programme: the 2026 incubation pipeline and a 2022 KRISHIBOOT incubatee pipeline); Mentoring and Resources ask the founder to pick the startup record first.
Mentoring: 0 relationships, 0 meetings, 0 feedbacks; 'No mentors available' in both of the founder's pipelines (each startup record maps to exactly one pipeline).
Learning: 0 sessions, 0 courses, 0 library items for this founder; the manager-side 'Test Session' is shared with five other pipelines and is not visible.
Events: /app/events opens for founders (titled 'Manage your event(s)') with a blank list; a-IDEA has 0 events.
Funding: /app/funding, /grant, /nominations and /recipients all give 'Permission denied' to a founder.
Announcements: 'Not authorized'; Noticeboard and Survey pages render blank for a founder; no noticeboard widget on the founder home.
No founder-side progress-report, monthly update or KPI form exists: the pipeline Updates tab is empty in every pipeline checked by the manager-side agents; the home 'remaining tasks' lists only Company Profile.
Founder can open by URL: /app/events, /app/tools (shows '53 open grievances', the site-wide count), /app/tools/documents (empty Applications folder) and the hidden admin /app/tools/certificate (Bulk Certificate Generator).
Grievance form: 2 issue types, 250-character title, 5,000-character details, optional file, reCAPTCHA; no programme or startup selector.
Chat: one conversation, the KRISHIBOOT 2.0 cohort group with 107 members and 4 unread; opening /app/chat auto-opens the thread and sends a read receipt (POST /message/readby, blocked here).
Inbox: 'No Mail'; Tasks: 'No Task(s)'; Calendar: no entries in October 2026; user-menu Meetings: 'No meetings found'.
Public marketplace (accubate.app/en): 187 programmes from 44 organisations (48 with a closing date), 7 events from 3 incubators, 6 offers from 2 vendors; a-IDEA lists 1 programme (KRISHIBOOT 10.0, marketplace says closes 29 Oct 2026, the form says 28 Oct).
Footer on every page: Support (grievance form), Feedback (mailto to the vendor), Terms of use, Privacy Policy; copyright 'Cunomial'.

Strengths

Every manager-side support module has a matching founder screen with the same structure (Learning hub cards, mentoring tabs, perks tabs), so the model is easy to explain.
Mentoring and perks are scoped per startup record and pipeline, so a founder in two programmes sees each programme's mentors and perks separately.
Clear empty states on most lists ('No mentors available', 'No sessions', 'No Tickets Raised, Raise your first ticket').
Sessions have useful filters (Virtual/Physical, Completed/Upcoming, Pipeline) and Courses have status chips.
Grievance raising is always one click away (top-bar icon and footer Support link) and the form is short.
The vendor's public marketplace gives cross-incubator discovery of calls, events and offers.

Gaps and friction

Most founder modules are empty at a-IDEA (mentors, sessions, courses, library, events), so the founder's app is a set of blank pages; there is no guidance on what the programme offers or when.
No founder view of funding: nominations, sanctioned amount, tranche conditions and utilisation reports are invisible to the startup ('Permission denied').
No founder-side periodic update, monthly report or KPI form at a-IDEA; the pipeline Updates feature exists but is not configured anywhere.
No 'documents issued to you' area: offer letters, agreements and certificates have no home on the founder side.
Announcements are email-only and never reach the in-app Inbox; the noticeboard is not shown to founders, so there is no in-app record of what the incubator told them.
Inconsistent route guards: founders can open the admin Bulk Certificate Generator, the events manager and the document store by URL, and see the site-wide open-grievance count.
Admin wording leaks into founder screens ('Manage your event(s)', 'Complaints, escalation levels and their settings').
The grievance form has no programme or startup field, so tickets cannot be routed to the right programme team; a character counter is misplaced under the radio buttons.
Cohort group chat has no moderation or pinned notices; a member posted a personal phone number to 107 people. Opening chat marks messages as read automatically.
Founders with two startup records must re-select the startup (and pipeline) on several pages.
The public marketplace is not linked from the founder app, and its closing date for a-IDEA's call differs by a day from the form's own date.

For INQB Zone

Give the founder one 'My programme' home that lists only what is switched on for their programme (mentors, sessions, perks, reports due, next tranche) and hide empty modules instead of showing blank pages.
Show founders their own funding: sanctioned amount, tranches released and pending, the condition holding the next tranche, and the UC or report due (our grants plugin should have a founder view).
Make periodic reports first-class for founders: the monthly health report window (1st to 5th) with reminders, a status per period, and the rule that late reports hold tranches, visible to the founder.
Add a founder 'Documents' tab with everything issued to the startup (offer letter, agreement, certificates, receipts), kept after the programme ends (MoU E4 already requires issued documents to stay in the startup's record).
Copy the founder-side mentor request flow but keep our decision that the PM books sessions; show who is available and why, and say plainly when a programme has no mentors yet.
Tie every support ticket to the startup and programme automatically from the signed-in context, route it to that programme's staff, and keep internal counts off founder screens.
Post every announcement into an in-app notice feed as well as email, so founders have a record.
Enforce role checks on the server for every route and API; never rely on hiding menu items (founders here reach admin tools by URL).
If we offer cohort chat, add moderation, pinned notices, and warnings or masking when phone numbers or emails are posted; do not mark messages read just by opening the page.
Our planned public directory of open calls (brainstorm decision) is a real feature at Accubate (187 programmes); ours should be linked from the founder app and use the call's own closing date.

What it means for INQB Zone

a-IDEA uses Accubate as an intake and email system. Calls, forms, rounds and result mails are busy; almost everything after selection (mentoring, events, learning, milestones, funding, invoices) sits empty and runs in spreadsheets and WhatsApp. That shapes what INQB Zone has to match and where it can win.

Match the intake on day one

This is the part a-IDEA actually uses: 87 pipelines, 164 forms, 7,081 applications, 569 announcements. INQB Zone v1 needs multi-round calls with a form per round, public and private rounds, a weighted rubric with evaluator workload and reminders, form versioning, the apply-link funnel, per-question charts and a mail log with delivery and open tracking.

Win after selection, where Accubate is empty

Mentoring has 0 relationships, there are 0 events, 0 courses and 0 fund records, and milestones read 0 / 0 everywhere. Here INQB Zone competes with spreadsheets, not with Accubate data. PM-led mentoring, monthly reports with real KPIs and a tranche engine tied to reports are new value, with nothing to migrate.

Bring pitch day and the committee into the system

KRISHIBOOT 9.0 and SIDBI Seed Fund 2026 had no evaluation form in any round. Screening, pitches and committee decisions happen outside Accubate, and only promote or reject is recorded. Pitch slots, committee decisions and minutes as real steps are the most visible gap to close.

One profile instead of field mappings

Accubate copies answers into a second Startup pipeline through 26 hand-built mappings, mostly incomplete. Only about 5 of 131 startups in the 2026 cohort filled the company profile, and many records still read 'Startup Name'. Seen from the founder side, a profile created 11 minutes after the application was submitted shows every field as 'Not updated yet', and revenue is asked in four unconnected places. INQB Zone's founder-owned venture profile with application snapshots removes the copy step.

Give founders a real app

The founder side is thin. There is no in-app list of open calls (founders arrive through public links), no evaluation feedback, 'No mentors available', 'Permission denied' on funding, and no progress-report form. Each onboarding creates a second startup record with its own ID. Meanwhile route guards leak: a founder can open the admin certificate generator and see the site-wide grievance count, and a 107-member cohort chat exposes phone numbers. A founder home with status, tasks, reports and support is a clear win.

Make setup one workspace, with drafts

Opening one call means visiting five builders (cohort, pipeline, form, mail, mappings) and dozens of round toggles that auto-save on a live call. A single Call workspace with round templates, sensible defaults and draft-then-publish is a clear, demonstrable improvement.

Fix the grievance desk

74 tickets, 53 still open; programme tickets go to about 20 staff at once, there is no reply thread and no escalation. Most tickets ask for results or report upload trouble near deadlines. One owner per ticket, SLA and escalation (as in MoU 19.2), plus a live application status for applicants, would cut the volume.

Lead with security and India-first defaults

MFA is off for all 6,252 users of a site holding 64 GB of documents; founders upload Aadhaar copies; AI is bring-your-own US keys; new calls are publicly listed by default; opening an application writes to it; numbers use Western grouping. INQB Zone's TOTP for admins and finance, no Aadhaar, India-only AI and lakh/crore formatting answer each point.

Plan the switch before 31 Mar 2027

a-IDEA's Accubate licence ends 31 Mar 2027 (169 days from capture). The decision should be due by about end of January 2027. Migration is mostly the startup register, active calls, form templates and the document store (58.6 GB of it is application files); staff seats are capped at 24 today.

Questions for the team

Migration scope: do we import a-IDEA's history (7,081 applications, about 64 GB of documents) or start clean with active calls and the 360-startup register, keeping Accubate exports as an archive?
Which intake features are must-have for v1: round model, weighted rubric, evaluator workload, form versioning, apply-link funnel, mail log? Which can wait for v1.x?
Do we put pitch-day scheduling and committee decisions in v1, given a-IDEA runs them outside Accubate today?
Founders today reach calls only through public links and never see feedback. What should the INQB Zone founder home show on day one: open calls, application status with feedback, monthly report due, mentor sessions, tickets?
Rebuild five or six call templates (KRISHIBOOT, AGRI UDAAN, NIDHI PRAYAS, SIDBI Seed Fund, NABARD CCF, BIRAC) by hand, or build an importer for Accubate's 164 forms?
How do we onboard 216 evaluators: guest evaluator links, PM-entered scores, or full accounts?
a-IDEA charges a ₹200 registration fee by bank transfer with a typed UTR. Is UTR verification by the finance role enough for v1, or do we need a payment gateway?
Should the pilot offer to take over the grievance desk (53 open tickets) with SLA and escalation as an early, visible win?
Do we lead the a-IDEA pitch with security (MFA off, Aadhaar uploads, US AI keys) or with the one-workspace setup? Who presents it?
What must be live by end of January 2027 so a-IDEA can decide not to renew Accubate on 31 Mar 2027?
Should we ask a-IDEA now for a full Accubate data export, so migration can be tested early?

How this was made

On 12 and 13 Oct 2026 Increeks signed in to a-IDEA's Accubate tenant with an incubator-manager account and then a startup (founder) account. The sign-ins were done by hand; the screens were then captured by agents driving that browser session, one per area, each in its own tab.

The script could only navigate: it refused clicks on any button that saves, submits, approves, deletes or sends, and it aborted every request to Accubate that could write data (edits, deletions, and any POST that was not a list or filter read). On 13 Oct, with Increeks' approval, two read calls were let through in their read-only form (the startup profile and the form questions), so the founder's profile could be captured. The application's round-by-round answers load through an automatic PUT, which stayed blocked, so that view is missing.

Before each screenshot the script blurred names of startups and people, emails, phone numbers and logos, using the names in the app's own data. Every screenshot was then checked by eye. The page text captured alongside stayed on the capturing machine and is not part of this guide.

A separate checker then went through every screenshot again at full resolution, tile by tile, and strengthened the blur wherever small text was still readable. That pass fixed about 40 of the manager screenshots, including a-IDEA's bank details on a public apply page.

Known side effect: opening the notification bell in the manager account marked its unread notifications as read. Every other write the pages tried (marking an application viewed, saving list filters, read receipts, visitor counts) was blocked.