it is understood that the invention is not limited to the particular methodology , protocols , and reagents , etc ., described herein , as these may vary as the skilled artisan will recognize . it is also to be understood that the terminology used herein is used for the purpose of describing particular embodiments only , and is not intended to limit the scope of the invention . it also is be noted that as used herein and in the appended claims , the singular forms “ a ,” “ an ,” and “ the ” include the plural reference unless the context clearly dictates otherwise . thus , for example , a reference to “ a processor ” is a reference to one or more processors and equivalents thereof known to those skilled in the art . unless defined otherwise , all technical and scientific terms used herein have the same meanings as commonly understood by one of ordinary skill in the art to which the invention pertains . the embodiments of the invention and the various features and advantageous details thereof are explained more fully with reference to the non - limiting embodiments and examples that are described and / or illustrated in the accompanying drawings and detailed in the following description . it should be noted that the features illustrated in the drawings are not necessarily drawn to scale , and features of one embodiment may be employed with other embodiments as the skilled artisan would recognize , even if not explicitly stated herein . descriptions of well - known components and processing techniques may be omitted so as to not unnecessarily obscure the embodiments of the invention . the examples used herein are intended merely to facilitate an understanding of ways in which the invention may be practiced and to further enable those of skill in the art to practice the embodiments of the invention . accordingly , the examples and embodiments herein should not be construed as limiting the scope of the invention , which is defined solely by the appended claims and applicable law . moreover , it is noted that like reference numerals reference similar parts throughout the several views of the drawings . the following preferred embodiments may be described in the context of a network - based system using host servers and client devices , such as the internet , and may be adapted to various devices and communication networks without departing from the overall scope of the invention . as shown in fig1 , embodiments of the invention may be applicable to business relationships between various entities including , for example , sponsor ( vendor ) companies 101 . the sponsors 1 - n 101 may be in communication over a network , such as the internet , and may be linked to participating members 1 - n 103 , 104 . members 103 , 104 may be in further communication with various customers 110 . sponsors 101 may include vendors or manufacturers organizations providing products or services through a distribution and fulfillment channel . through the system sponsors 101 may provide rewards or incentives when their products and services are sold through the channel . partner or reseller organizations of sponsors 101 may include members 103 who may be affiliated 102 to their respective sponsors 101 , such as by participating in partner programs , that may include obtaining vendor specific competencies , and the like . members 103 , 104 serve their customers 110 by providing solutions to their technology challenges and fulfill their needs with products and / or services 106 offerings . when customer needs or opportunities 107 extend beyond what a single member , e . g . member 103 , can provide , the system may allow a participant , such as member 103 , to search for , solicit support from and / or partner with other members 104 to fill out the missing offerings and create a joint value proposition for the opportunity . when an opportunity 107 is brought in to the network , the member who owns the customer relationship is defined as the managing partner ( member ) 103 and those assisting in its execution as the supporting members or partners , e . g . member 104 . an opportunity 107 may include the state or period of time during which the managing member 103 is estimating the overall project requirements , negotiating with possible supporting members 104 on what each would provide to the overall job / project effort 109 . as part of this process , the effort or opportunity 107 may be broken into specific line items 108 whereby each line may represent a product fulfillment or services task . each line item 108 may also be mapped or associated to a single sponsor 101 , although some line items may not . an example would be a line item which covers the purchase of a particular brand of computer servers , in which the brand manufacturer may become the sponsor for the respective line item 108 . sponsors may allocate member rewards and incentives 105 as a function of the line items which apply to them , e . g . through the use of a promotion managers and the like . during the opportunity stage 107 , estimated reward amounts may be given by the sponsor 101 through the system in a sponsor programmed or manual fashion . for example , a manufacturer may have a predetermined incentive applicable to a designated product that is applicable to opportunity 107 , and / or may present targeted incentives to a particular opportunity 107 based on requests or other parameters . thus , the system may support a broad and flexible mechanism for sponsors to offer incentives to participating members , and also encourage collaboration between participating members that use common rewards such as collaboration currency . the overall job / project 109 may be registered with each participating sponsor 101 via a single - step , once a customer 110 commits to moving forward with the opportunity ( in part or as a whole ). thus , the overall effort may mature from an opportunity to a registered collaboration 107 , including predetermined sponsor - provided incentives 105 . at the point of collaboration , reward commitments from sponsors 101 may determined and placed in abeyance for each applicable registered item , such as line items 108 . the sum of all rewards mapped to a collaboration entity may be held by the system until the work is completed and a claim or proof of performance is made by a responsible party , such as a managing partner for each line item 108 . on a line by line basis , once the line item claims are approved by the system , the reward funds 112 may be transferred to the collaborating members 103 , 104 in a manner pre - determined by the members 103 , 104 yet controlled by the managing partner 103 , as shown in 111 . in embodiments , reward funds 112 earned through incentives 105 may include collaboration currency , that the system may recognize for further functionality , such as various redemption services . additional aspects regarding an exemplary opportunity , collaboration and rewards lifecycle are with reference to fig2 and 3 . as mentioned above , exemplary systems and methods may be implemented by way of a web - based platform such as shown in fig2 . in embodiments , the system may allow members , such as a user 203 , access through system clients 201 including , for example , web and mobile browsers 202 , 204 , as well as external systems and other clients 205 which may access the platform through a web service based application programming interface ( api ) 208 or application layer . external systems could be line of business systems , sites or programs which members or sponsors connect to the platform . exemplary core system 206 may be subdivided into layers , or modules configured according to programming instructions running on one or more microprocessors . each layer / module may be configured to serve a specific purpose , and may , for example , be configured to reside on a single server , or multiple servers such as in a web farm environment . as shown in fig2 , exemplary layers / modules may include presentation layer 207 , application layer 208 , domain layer 209 and infrastructure layer 210 . the presentation layer 207 may include a web server layer configured for receiving and dispatching instructions from clients as well as presenting views and user interfaces . this layer may be based on a pseudo model - view - controller ( mvc ) pattern and may be , for example , configured as a client itself of the application layer 208 . the actual model resides in a domain layer 209 . the application layer 208 may include services which coordinate tasks and delegate work to business objects in the domain layer 209 . the application services may be configured to act as a remote facade to business objects and rules which inherently define the system . a domain layer 209 layer may include system logic , containers , objects , structures , factories and rules of the business aspects of the system . such features provide various functionality to the system , and facilitate and / or make available the business objects , and entities , to the system for processing and handling . an infrastructure layer 210 may be configured to hold elements that are required , for example , as part of modern web platforms . this layer may include , for example , cross cutting concerns such as logging , data i / o , security , integration and others . behind the infrastructure layer 210 , back - end systems 211 may be used to further support the platform . these may include web platform building blocks and include reporting services 212 , database servers 213 and other systems 214 , processes or methods as required . fig3 illustrates aspects of three “ lifecycles ” or high level processes which may be performed according to systems and methods described herein . a first cycle 301 may be initiated , for example , when a user first joins 302 the network . once a user is setup and their company is registered as a member , the user can login and use the discover and connect features 309 or proceed to an opportunity or collaboration 316 . the signup process 301 may include a multi - step process whereby after the first step 302 a user may create a user account 303 . based on authentication credentials , which may be provided in 303 , a validation process may be initiated to ensure , for example , the use of a valid email address in 304 . the method may continue with 306 . in step 306 a determination may be made as to whether a member company profile exists . if a corresponding member company profile exists , the user may be joined to the existing company in step 307 , e . g . if the user has an invitation to do so . otherwise , a new member company account may be created in step 305 , which may also be validated in step 308 , such as through the various sponsors they represent in industry . this validation may be automated , such as by automatically sending confirmation messages , scanning white lists , and the like , or done through a manual process by the sponsors . exemplary systems may allow for more than one user to be assigned to a single member company . once users are setup , they may login 323 to the system and can navigate various features , such as those features with permissions assigned to the corresponding member company or individual user . for example , the user may be provided access to the discover and connect section 309 , in which users may be given tools to find partner members 312 , such as by specifying desired attributes they desire partners to have . these attributes can be , for example , location based and / or driven by sponsor qualifications and staff certifications . search 312 can also be refined by the use of keywords and other techniques known in the art . in embodiments , members can select specific partners to become “ preferred partners ” 313 , which may be used , for example , to simplify communications and / or restrict opportunity item routing . throughout the system , users may be allowed to get a member company &# 39 ; s profile , such as in by viewing a potential or actual partner in step 311 , and may be allowed to connect with the partner by contacting predetermined key contacts in connect step 315 . ratings may also be assigned , for example by an authorized user , to members in step 314 , which may be used , for example , to measure and report on a member &# 39 ; s effectiveness in collaborating on efforts , the member &# 39 ; s ability to influence business opportunities , and other criteria relevant and / or unique to the collaborative environment . for example , according to embodiments , a member may be ranked based on a demonstrated ability to partner in a particular collaborative role , such as service support and / or product delivery related to line items of a project . thereafter , users may be better able to evaluate not only the member &# 39 ; s ability to deliver a product or service to a customer , but their effectiveness in delivering the product or service in a particular collaborative context , such as supporting partners in geographic regions , supporting designated service - type partners , and the like . another area available to user is depicted as get insight step 310 and may include additional collections of information , based on , for example , web based tools including industry content , blogs , wikis and discussion forums , from which targeted information may be obtained . with further reference to fig3 , a registered user may also access a business lifecycle of the system depicted as a collaborate and earn process 316 . process 316 shows aspects of an exemplary business flow , highlights of which are discussed below . leads 317 are typically sourced from vendors or other third party sources . a lead may or may not precede an opportunity 318 , and may be targeted to specific members or select group ( s ) of members ( e . g . preferred partners ), or published to the entire network based on screening criteria . opportunities 318 are managed by members ( managing partners ). they may be created directly in the system , e . g . by authorized users , or by converting a lead 317 . supporting partners may be solicited and selected to assist / share work . in embodiments , supporting partners must be members or become members to qualify for any benefits available through the network . collaborations 319 are registered opportunities 318 that have been toggled by a customer approving the project . collaborations line items may be individually registered with sponsors , and sponsors may authorize reward funding upon the registration , as discussed herein . claims 320 result from performance of line items according to registered opportunities 318 , and may be used to award rewards performed by the managing partner on a line item basis once a work item is completed . a claim 320 with proof of performance may be submitted to the system . once approved , pre - designated incentives , such as collaboration currency , may be issued from vendors and distributed , for example , by the managing partner . rewards may be issued and distributed in step 321 , and may include , for example , funds expressed in collaboration currency . rewards may be converted to , for example , cash , transfers / shares for supporting partners , system subscription dues , and / or member services catalog which may provide options , such as , business - related services from authorized third - party providers to help members improve their business &# 39 ; performance . fig4 provides additional details regarding exemplary systems and methods including aspects of an incentive accounting program . as shown in fig4 , sponsors may set up their reward promotions 401 and designate how the promotions may relate to opportunities , collaborations 408 and the claim process 414 . in order for rewards to be made available to a member , the system provides sponsors with tools to create the promotion beginning in step 402 , e . g . to set business rules on work items which drive funding types , and to set applicable rewards in step 403 , as well as their applicability such as partner related parameters , e . g . partner tier , competency requirements , etc ., and product parameters , e . g . types , categories , product requirements , etc ., in steps 404 and 405 , respectively . other parameters may be set according to sponsor preferences in step 406 , e . g . time limits , etc . the collection of promotions from multiple sponsors may be accomplished in step 407 and may be used for a promotion catalog which is used by the system to estimate various rewards 411 on work items 410 during the opportunity and collaboration phases 408 , and to attribute actual rewards 416 upon the submission of actual work item claims 415 . with further reference to fig4 , opportunity / collaboration cycle 408 may include assigning line item responsibilities 410 of collaboration 409 to various supporting members 413 by a managing partner 412 . for example , as discussed further herein , a managing member may be determined in step 412 , and supporting members assigned in step ( s ) 413 . based on these designations , a collaboration may be created in step 409 , including various line item related rewards 411 . as line items designated in step ( s ) 410 are completed , claims may be verified in step ( s ) 415 , and rewards 416 processed to designated supporting accounts 419 via managing account 418 . for example , the rewards earned may be distributed in step 417 , such as by a managing account approval in step 418 , to the other supporting members in step 419 . as discussed herein , the disclosed systems and methods may provide a partnerconduit ( pcn ) that may include a business - to - business ( b2b ) application enabling independent reseller and influencer organizations ( partners ) to aggregate and monetize the benefits of marketing programs from multiple manufacturer / vendor organizations ( vendors ) and to redeem , reinvest or reallocate them using a common media , such as collaboration currency . unlike current partner relationship systems ( prm ), wherein a vendor can manage its own proprietary joint marketing fund , deal / opportunity registration and promotional marketing programs in a stand - alone environment , pcn replaces the stand - alone environment with a multi - vendor approach that enable partners to tap in to reseller marketing benefits the same way they conduct their b2b customer business , thereby combining the products / services of multiple vendors and their own resources to provide a unique customer solution . unlike the proprietary partner ecosystems , built on proprietary or prm technologies , which are maintained by leading vendors ( and desired by smaller vendors ), the pcn encourages and facilitates partners finding other qualified partners with whom they can collaborate across industry boundaries . for example , when partner a can provide most of a unique customer solution using vendor 1 and vendor 2 products , but lacks some capability such as domain expertise , industry / vendor recognized certifications , vertical industry experience or geographic coverage to provide a complete solution , through the pcn application they can find partner b with the verified bench strength and complementary skill sets to complete the specified assignment in the context it is needed . and when partner b has the certifications and credentials to support the customer requirements for vendor 3 products , the customer can be assured that they are using authorized , expert solution providers for the entire assignment . as described above , a partner rating system provides pcn members with insight into how effective potential partners are at working collaboratively , and can provide additional specialized information that is relevant to the particular collaboration project at hand . current ranking systems and methods do not provide comparable information in a format to facilitate effective collaboration . additionally , by designing the interface from the partners &# 39 ; perspective and on - boarding vendors via a common process , pcn enables partners to access all the participating vendors via a single interface rather than having to navigate many different vendor programs independently , in a resource - intensive process . since most partners have more ‘ active ’ vendor relationships ( e . g . 20 - 30 ) than they typically manage to engage fully with ( e . g . 4 - 6 ‘ strategic ’ vendors ) based on the way vendors approach them , the pcn allows them to take more comprehensive advantage of all their ‘ active ’ relationships , such as by putting them in a profile once and then any time they are using a specific vendors &# 39 ; eligible products / services in a customer opportunity , the system tracks its value in marketing funds , e . g . collaboration currency . this may enable a partner to more efficiently source and sell multi - vendor solutions which their customers demand but for which the reporting burden often left joint marketing funds or promotional marketing rewards unclaimed . the system may create reporting templates , using vendor pre - authorized business rules that can automate such aspects as the lead distribution , registration , calculation , tracking and validation of all participating vendor product / services opportunities . for vendors , this enables them to participate in a network or coalition of complementary products and services , combining their products and services with the products / services of other vendors in the system under the management of a professionally certified and authorized partner , while maintaining control of the business rules impacting their participation and funding of joint marketing funds / promotions . the application may track partner - identified collaborations throughout the entire opportunity lifecycle ( lead - registered opportunity - sold - delivered - claimed ), and shift control of the currency from vendor to partner upon completed proof - of - performance . for each opportunity there is a managing / lead partner ( partner a ) and one or more participating / support partners ( partner b ). for example , if partner a identified and qualified an opportunity with a b2b customer requiring products / services including hardware ( vendor 1 ), general business software ( vendor 2 ), and a vertically specialized application software ( vendor 3 ) and also required partner b to provide authorized service and support on vendor 3 products , then the entire transaction may be entered and tracked within the pcn application . since vendor 1 and vendor 3 are both participating in pcn , the system may automatically track the revenues value and the collaboration currency commitment values based on each vendor &# 39 ; s customizable set - up . in this example , vendor 1 is funding collaboration currency ( cc $) at a rate of 1 . 25 % of the revenue value , while vendor 3 is funding at a rate of 1 %. vendor 2 is not in the pcn but the full details of the transaction are captured for the convenience of partner a as the managing partner . partners within the network are encouraged to share or redistribute common currency to contributing partners that collaborated during the sale / delivery process , reinvest via network authorized service providers through a direct payment process to organizations providing services to promote business growth or offset business expenses , or they may redeem their collaboration currency for cash in their local currency . thus , the disclosed common rewards currency used within the system is readily usable across boundaries , such as those arising from international borders and monetary currencies , in that the currency is fully useable within the system without reference to external exchange value and the like , until the time of redemption . in the example above partner a designates that 50 % of the 650 in collaboration currency is to be shared with partner b , or it could have designated that all or any percentage of the collaboration currency be redistributed to partner b — at their discretion but in a manner transparent to partner b using the share function that is automatically managed within the system . independent of the desired allocation of collaboration currency designated by the managing partner , each of the entities may derive incremental benefits through participation in the network and use of the application . for example : partner a benefits by retaining / growing an existing customer as well as through the efficiency of capturing marketing funds from a single process and from all participating vendors . partner b benefits by finding new business that may not have surfaced via other business development activities as well as from the potential for collaboration currency from partner a . vendor 1 found new business and often at a lower operational cost than other sources of new business . vendor 3 gets new business through a source that , heretofore , would have been very difficult to discover were it not for the partner - to - partner collaboration . embodiments of the present invention can include various configurations and systems for implementing the described methods , as well as computer - readable storage medium coded with instructions for causing a computer to execute the described methods . for example , as shown generally in fig5 , an electronic system 500 including a processor , a memory and an electronic communication device may be configured to initiate , forward , and / or receive , user registration , collaboration requests , and / or rewards distributions to , from and / or via a supporting server 550 . one or more servers 550 - 554 may be configured to receive and process user requests , collaborations , vendor incentives , rewards , etc . the system 500 may represent a user computer system , wireless communication devices such as 520 , 570 , subnetworks such as 530 , 590 , a server , or any other network - capable device with the requisite functional capabilities . the system 500 and servers 550 - 554 may include any number of processors ( not shown ) that are coupled to storage devices including a first storage ( not shown , typically a random access memory , or “ ram ”), second storage ( not shown , typically a read only memory , or “ rom ”). both of these storage devices may include any suitable type of the computer - readable media described and / or mentioned above . a mass storage device ( not shown ) may also be used to store programs , data and the like and is typically a secondary storage medium , such as a hard disk that is slower than primary storage . it will be appreciated that the information retained within the mass storage device , may , in appropriate cases , be incorporated in standard manner as part of primary storage as virtual memory . a specific mass storage device such as a cd - rom may also pass data uni - directionally to the processor . as conventionally known in the art , a computer system , such as system 500 , may also include an interface that includes one or more input / output devices such as such as video monitors , track balls , mice 504 , keyboards , microphones , touch - sensitive displays , transducer card readers , magnetic or paper tape readers , tablets , styluses , voice or handwriting recognizers , or other known input devices , including other appropriately linked computers 510 . the system 500 may be coupled to a computer or other electronic communication network 570 , 580 using a network connection as shown generally at 501 . the network can connect various wired , optical , electronic and other known networks to exchange information among computers 510 , servers 550 - 554 , 580 , wireless communication devices 520 , 570 and sub - networks 590 , 530 . with such a network connection , it is contemplated that the system 500 and the processor ( s ) therein may receive information from the network , or may output information to the network in the course of performing the above - described method steps . for example , a request to register a user , a collaboration , and / or an incentive may be forwarded from a system 500 to a server 550 via network 501 . in embodiments , network server 550 may access information stored in another server or data source 552 in order to , for example , validate a requesting user , access account information , incentive details and the like . after the request is evaluated , a response may be sent from the server 550 to the system 500 via network 501 , or other means . the above - described devices and materials will be familiar to those of skill in the computer hardware and software arts and need not be individually or exhaustively depicted to be understood by those of skill in the art . the hardware elements described above may be configured to act as one or more units for performing the operations described above . in addition , embodiments of the present invention further include computer - readable storage media that include program instructions for performing various computer - implemented operations of the described methods . the media may also include , alone or in combination with the program instructions , data files , data structures , tables , and the like . the media and program instructions may be those specially designed and constructed for the purposes of the present subject matter , or they may be of the kind available to those having skill in the computer software arts . examples of computer - readable storage media include magnetic media such as hard disks , floppy disks , and magnetic tape ; optical media such as cd - rom disks ; magneto - optical media such as floptical disks ; and hardware devices that are specially configured to store and perform program instructions , such as read - only memory devices ( rom ) and random access memory ( ram ). examples of program instructions include both machine code , such as produced by a compiler , and files containing higher level code that may be executed by the computer using an interpreter . the invention has been described with reference to exemplary embodiments . modifications and alterations of the described embodiments may be evident to those of ordinary skill in the art upon a reading and understanding of this specification . the present invention is intended to include all such modifications and alterations insofar as they come within the scope of the appended claims , or the equivalents thereof .