1. Project Assessment & Estimates 1

2. Concept Retailer Experience

3. Login Password Continue

4. Campaign 123Sent 03/15View DetailsPerformance Metrics Campaign ABCSent 02/15View DetailsPerformance Metrics Campaign DEFSent 01/15View DetailsPerformance Metrics Campaign 456Sent 01/10View DetailsPerformance Metrics Create Campaign Welcome John Logout COMPLETE DRAFT COMPLETE

5. STEP 1 => Select Customers Continue Filter By Segment Distance From Store John’s Campaign Campaign Name 4,500# of Customers of Type A 5,500# of Customers of Type B 10,000 Total Selected

6. STEP 2 => Select Template Send Email Template 1 Template 2 Template 3 John’s Campaign # of coupons

7. Send Email Coupon 1 STEP 3 => Select Coupon John’s Campaign EditViewDelete Coupon 2 EditViewDelete Coupon 3 EditViewDelete Total Coupons Selected = 3 / 6 Create Coupon

8. HTML Editor for Coupon STEP 3 => Select Coupon John’s Campaign Save Coupon Type

9. Concept Administrator Experience

10. Welcome John Logout OrdersSetup 1)Essentially see a list of all the campaign orders here 2)Have the ability to filter campaign orders by Retailer 3)Perform specific functions like Cancelling Orders (?) View Order Details Print etc

11. Welcome John Logout OrdersSetup A lot of system setup (where the data will come from, print fulfillment vendor setup etc Permissions and Roles Based Access Control Etc etc

12. High Level Architecture

13. Application Oracle DB Market Lists Coupons Orders Print Vendor Email Vendor Retailer Administrator High Level Architecture

14. Key Architecture Assumptions  Input Customer Data is at an aggregate level  Output will be an XML file generated regularly. All downstream processing will be handled by Targetbase  Retailer, User, Role setup is done in Targetbase Databases and sent to this system.  There is a hierarchy of roles (Region, District, Store) that will be managed by Targetbase  Limited Workflow + Rules Engine capabilities .NET Based Architecture  Production Environment provided by TargetBase

15. Key Assumptions Around Roles  Inkriti ‒ Wireframes ‒ Creative ‒ Build ‒ Deploy ‒ Train ‒ 30-day warranty  TargetBase ‒ Owner to join Inkriti daily standups ‒ Provide Staging and Production Environment ‒ Provide input data + process output data

16. Inkriti Agile Development Methodology  User Stories  Daily Stand up calls  Weekly Sprints

17. Example Project Plan & Milestones Content 20 th Feb Inkriti Tasks Agency Tasks Milestone Date Sprint 0 Acceptance QA Transition 13 th March First Set of Features Available for review Kickoff Sprint 1 27 st Feb Sprint 2 6th March 13 th Feb Sprint 3 Wireframes Infrastructure 20 th March Revisions Sprint 4 5 th April Handoff Go Live Ready Creative PATT Feedback

18. PATT Website – Sprint Details Example Sprint Details

19. Time & Cost Estimates  3-5 Months  Team ‒ 2.5-3 developers ‒ 1 “man-person” (PM, BA, QA, Sys Admin roles) ‒ Total = 3.5-4 people  Approximate Cost ‒ $150 -$280K

20. INKRITI LLC Harry Spitulnik 1101 Worcester Road Framingham, MA 01701 (508) 532 – 8441 hspitulnik@inkriti.com