| Positioning area | What Pingmedia will communicate | What Pingmedia will avoid |
|---|---|---|
| Core identity | AI-enabled professional foundation for non-technical learners. | “Become an AI expert in 45 days.” |
| Learning model | 45 guided classes, weekly projects, trainer feedback, capstone demonstration. | Long lectures or daily introduction of unrelated tools. |
| Career promise | Resume support, interview preparation, portfolio building, placement assistance. | Guaranteed employment or unrealistic salary claims. |
| Technical depth | No-code and AI-assisted building with guided troubleshooting. | Python, model training, APIs, full-stack engineering, or advanced agent frameworks. |
| Business value | Research, communication, content, analysis, lead workflows, and websites. | Fully autonomous systems without human review. |
| Admission requirement | Minimum standard | Why it matters |
|---|---|---|
| Laptop | Personal laptop with current browser, working audio, and charger. | Every class contains an individual build or practice activity. |
| Digital basics | Comfortable using email, browser tabs, Google Drive, file uploads, and basic documents. | The program is non-technical, but not mobile-only. |
| Accounts | Active Google account and willingness to create free accounts on selected AI platforms. | Needed for course projects and workflow connections. |
| Language | Comfortable learning in Hinglish and producing professional outputs in English. | Matches local learning comfort and employment requirements. |
| Commitment | Attend five days per week and submit weekly portfolio outputs. | Skill development depends on repetition and feedback. |
| Participant type | Guided website project | Minimum required features |
|---|---|---|
| Student / Job Seeker | Portfolio and career profile website | About, skills, projects, resume CTA, contact form |
| Working Professional | Professional profile or resource website | Expertise, work samples, resource section, enquiry form |
| Business Owner | Business landing page | Offer, proof, services, FAQ, lead form, contact CTA |
| Shared skill | Student brief | Professional brief | Business-owner brief |
|---|---|---|---|
| Research | Employer and target-role analysis | Project or industry brief | Competitor and customer brief |
| Writing | Application and interview communication | Report, SOP, manager update | Sales, customer, vendor communication |
| Data | Placement or job dataset | Productivity or performance dataset | Lead, sales, or customer dataset |
| Presentation | Career portfolio | Management proposal | Sales or growth deck |
| Workflow | Application tracker | Meeting/action workflow | Lead enquiry and follow-up |
| Website | Portfolio site | Professional profile site | Business landing page |
| Certification requirement | Standard | Action if incomplete |
|---|---|---|
| Attendance | Minimum 80% | Make-up plan before Demo Day; no automatic waiver |
| Mandatory projects | Prompt/context, data, video, workflow/agent, website, capstone | Certificate held until resubmission |
| Responsible AI test | Pass privacy, verification, copyright, and human-approval scenarios | Mandatory reassessment |
| Viva | Explain tool choice, context, errors, verification, and business/career value | One structured second attempt |
| Portfolio integrity | Individual work with source and AI-use disclosure | Plagiarised or copied work rejected |
| Capstone checkpoint | Required evidence | Trainer approval question |
|---|---|---|
| Problem definition | User, pain point, current process, desired outcome | Is the problem specific and useful? |
| Context pack | Sources, rules, examples, constraints, approved facts | Can another reviewer understand the operating context? |
| System design | Tools, workflow, inputs, outputs, approval points | Is the system appropriate for a beginner project? |
| Testing | Normal test, bad-input test, missing-data test, failure notes | Does the learner understand limitations? |
| Value | Time saved, quality improved, clarity created, or conversion supported | Is the value credible and not exaggerated? |
| Presentation | Live demo, slides, portfolio case study, viva | Can the learner explain without jargon? |
| Beginner service | Minimum portfolio proof | Important boundary |
|---|---|---|
| AI-assisted presentation creation | One strong 8–10 slide deck and revision log | Client provides verified facts and brand assets |
| Research and report preparation | Source-backed research brief | No medical, legal, or financial authority claims |
| Resume / LinkedIn optimisation | Career pack and job-description analysis | Never fabricate experience or achievements |
| AI image / short video package | Image set and 10–15 second video | Credit, copyright, and revision limits defined |
| Basic website development | Published website with test checklist | No complex backend or security claims |
| Lead workflow setup | Working approved enquiry workflow | Human review remains in the process |
| Stage | Trainer action | Required evidence |
|---|---|---|
| Before each week | Test all tools, credits, links, files, prompts, workflow connections, and fallback options. | Weekly readiness checklist |
| Before each class | Open clean demo accounts, duplicate student files, prepare three audience briefs, reset demo state. | Class folder + blank starter file |
| During demonstration | Narrate decisions, mistakes, checks, and why one tool or method was selected. | Trainer demo recording or notes |
| During practice | Observe learner screens, log common errors, avoid taking over the learner’s mouse unless necessary. | Error log and support notes |
| After class | Review sample submissions, publish corrections, update FAQs, and flag learners needing intervention. | Daily review note |
| After each week | Score portfolio outputs, conduct short feedback clinic, and update next-week pacing. | Rubric scores + action plan |
| After batch | Review completion, tool costs, incidents, learner feedback, outcomes, and curriculum changes. | Batch retrospective |
| Area | Recommended operating model | Control |
|---|---|---|
| Laptop | Personal laptop compulsory; charger and current browser required. | Device readiness check before Day 1 |
| Internet | Primary high-speed Wi-Fi plus backup hotspot/router. | Test before video and website weeks |
| Accounts | Learners use personal accounts; trainer accounts used for demos and selected premium features. | No shared passwords |
| Course files | One batch Drive with read-only master files and individual learner folders. | Naming and access policy |
| Paid credits | Fixed allowance for mandatory graded image/video/build tasks. | Usage sheet + approval for extra spend |
| Automation | Trainer-controlled templates; learners connect their own Google accounts where practical. | Remove access and rotate keys after batch |
| Fallback | Every premium exercise has a free or trainer-demo alternative. | Fallback documented in lesson plan |
| Data | Only simulated company data and learner-owned files. | No live client or confidential data |
| Risk | Early warning sign | Control action |
|---|---|---|
| Tool overload | Learners remember names but cannot repeat tasks | Limit mastery tools; use alternatives only for comparison |
| Mixed-cohort mismatch | Owner or professional finds student task irrelevant | Prepare three application briefs for role-sensitive lessons |
| Weak practice | Trainer demo takes most of the hour | Protect 25 minutes of individual build time |
| Copied portfolio work | Identical prompts, screenshots, or explanations | Individual data, viva, version history, and reflection required |
| Unverified output | Fluent answers accepted without source checks | Verification field in every relevant rubric |
| Unsafe automation | External messages or changes happen automatically | Mandatory human approval in all beginner workflows |
| Credit overspend | Repeated generations without planning | Fixed allowance, prompt planning, attempt log, approval for extras |
| Placement overpromise | Admissions discussion implies guaranteed employment | Written placement-assistance disclaimer |
| Tool change | Feature, price, or access changes mid-batch | Outcome-based lesson design and documented fallback |